> For the complete documentation index, see [llms.txt](https://docs.logsail.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.logsail.com/api-platform/logsail-apis/dataplane-apis.md).

# Dataplane APIs

LogSail is broken out into multiple APIs under different subdomains. All LogSail APIs are fully documented using OpenAPI and Swagger specs. Our public APIs include:

### Core API

Configure remote agents, querying metrics, and search through log data.

{% embed url="<https://core.logsail.com/docs>" %}

### Analytics API

Query usage reports on CPU and memory metrics.

{% embed url="<https://analytics.logsail.com/docs>" %}

### Intake API

An ingest API where agent entities push logging and metrics data to.

{% embed url="<https://intake.logsail.com/docs>" %}

### Entity Constructs and User Access

LogSail's Core and Auth APIs include several low level entities for controlling data streams and user access to data. Group Tenancies are used for controlling the relationships between specific users and resources supporting RBAC policies and&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.logsail.com/api-platform/logsail-apis/dataplane-apis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.