> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/v1/interfaces/apis/core-apis.md).

# Core APIs

Product-facing reference for `platform-api`, the gateway that exposes tenant resource listings, log search, and other platform-level operations. Paths in this section are relative to `https://<DATAOS_FQDN>/platform-api`; see [Authentication](/references/v1/interfaces/apis/core-apis/authentication.md) for the full base URL.

### What you can do

<table><thead><tr><th width="158.830078125">Capability</th><th>What it covers</th></tr></thead><tbody><tr><td><strong>Tenant resources</strong></td><td>List apps and links registered for a tenant, with product-based filtering.</td></tr><tr><td><strong>Log search</strong></td><td>Search logs for a specific tenant resource, grouped by pod/container.</td></tr></tbody></table>

### Start here

* [Authentication](/references/v1/interfaces/apis/core-apis/authentication.md): Use a Bearer token or an `apikey` header, plus optional tracing headers.
* [API Reference](/references/v1/interfaces/apis/core-apis/api-reference.md) : Find endpoint groups and detailed request/response behavior.


---

# 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://v2.dataos.info/references/v1/interfaces/apis/core-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.