> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/api-reference/beta-api/partner-api.md).

# Beta API

The Archera Beta API provides early access to features under active development — account-level\
billing data, new report types, and capabilities that haven't yet graduated to the stable API\
surface. Use it to build ahead of general availability, prototype integrations against real\
production data, and give feedback that shapes how these features ship.

Built for developers who need more than the stable API today, the Beta API lets you pull per-account\
cost breakdowns, access emerging data models, and integrate new capabilities directly into your\
platform. All endpoints are versioned at /beta/v1 and authenticated with your existing API key — no\
separate credentials required. Expect a faster release cadence and a shorter path from request to\
endpoint than you'd find anywhere else in the API.


---

# 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.archera.ai/api-reference/beta-api/partner-api.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.