> ## Documentation Index
> Fetch the complete documentation index at: https://developers.octaviatech.app/llms.txt
> Use this file to discover all available pages before exploring further.

# What is Octavia

> The platform behind Octavia's APIs — one account, one dashboard, many services.

The **Octavia Developer Platform** is a set of backend services you activate from one
dashboard and call over one consistent API. Each service is activated independently,
scoped with your own API key, and metered on its own plan — so you start with exactly
what you need and turn on the rest when you outgrow it.

<Card title="Octavia Developers Hub" icon="earth" href="https://octaviatech.app" arrow="true">
  The product surface behind the APIs.
</Card>

***

## One platform, several services

| **Service**  | **What it does**                                                                       | **Reference**                                          |
| ------------ | -------------------------------------------------------------------------------------- | ------------------------------------------------------ |
| **AI CMS**   | Create, localize, search and publish content, with AI drafting built in.               | [AI CMS reference](/api-reference/ai-cms/introduction) |
| **Storage**  | Store and serve files with signed URLs and access controls. Documentation in progress. | —                                                      |
| **Auth**     | Accounts, sessions and identity for your product.                                      | Documentation in progress.                             |
| **Payments** | Charge and reconcile payments. Documentation in progress.                              | —                                                      |

<Note>
  **AI CMS** is the only service with a full reference today. Everything else is
  activated from the dashboard and will get its own tab here as its reference lands.
</Note>

***

## What every service has in common

Whichever service you pick, the shape of the work is the same.

* **One dashboard.** [dashboard.octaviatech.app](https://dashboard.octaviatech.app)
  is where you activate services, create keys, and watch usage.
* **One team per workspace.** Every resource belongs to a team, and keys belong to
  that team — see [Teams & API keys](/platform/teams-and-keys).
* **One key per service.** A key is scoped to a single service, so a key for another
  Octavia product never counts against your AI CMS allowance.
* **One header.** Every call is authenticated with `x-api-key`. There is no second
  header for you to set — see [Authentication](/api-reference/ai-cms/authentication).
* **One envelope.** Every service answers with the same
  `{ success, statusCode, message, data }` shape, so your error handling is written
  once — see [Response format](/api-reference/ai-cms/response-fromat).

***

## How to read this documentation

The docs are split into two tabs, and they answer different questions.

| **Tab**    | **Use it for**                                                                                                                            |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Guides** | Platform-level questions: what the platform is, how to set up a workspace, how to keep a key safe, what to build next, where to get help. |
| **AI CMS** | The API itself: authentication, the content model, every endpoint, and the SDKs.                                                          |

<Info>
  Ready to make a call? The [Quickstart](/quickstart) walks a new workspace from
  sign-up to a working API key in about five minutes.
</Info>

***

## Conventions used across the docs

A few things hold everywhere, so they are stated once.

* **Identifiers are 24-character hex strings** (MongoDB ObjectIds), passed in the
  path or the body.
* **Slugs are URL-facing** and unique. Most create endpoints accept one explicitly;
  some derive it from the name.
* **Multilingual fields are maps** from a language code to a string, e.g.
  `{ "en": "Hello", "es": "Hola" }`.
* **Timestamps are ISO 8601** in UTC.
* **`x-api-key` is the only header you send.** Multi-tenancy headers are attached by
  the gateway, and no SDK option accepts them.

***

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart" arrow="true">
    From sign-up to a working key.
  </Card>

  <Card title="Teams & API keys" icon="key-round" href="/platform/teams-and-keys" arrow="true">
    How access is structured across a workspace.
  </Card>
</CardGroup>