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

# Core concepts

> The words that appear in Sigmora requests and responses, what each one means, and where its id comes from.

## Your account

| Term | Meaning | How you use it |
| - | - | - |
| **Workspace** | The private space owned by a person or team. It holds the credit balance, projects, Brands, products and connected accounts. | Nothing to send: your API key selects the workspace. |
| **API key** | A secret beginning `sk_live_` that authorizes requests for one workspace. | Create it in [**Settings → API keys**](https://sigmora.org/en/settings/api-keys). See [Authentication](/authentication). |
| **Role** | What the key's owner may do. | A `viewer` can read; an `editor` can create work and spend credits. |
| **Credits** | The unit every capability is priced in. | `GET /v1/capabilities` lists prices; every paid response reports what it charged. See [Pricing](/pricing). |

## Your work

| Term | Meaning | Where it comes from |
| - | - | - |
| **Capability** | One operation that produces something, such as writing a script or rendering a video. | `GET /v1/capabilities` lists them with price and availability. |
| **Project** | The container related work is filed in: scripts, footage, renders and the conversations that made them. | `POST /v1/projects`, then pass `project.id` as `projectId` on every capability call. See [Projects](/projects). |
| **Asset** | A piece of media stored in a project, such as uploaded or imported footage. | `GET /v1/assets?projectId=...` lists them; `POST /v1/assets/import` adds one from a URL. |
| **Job** | Long-running work that continues after the first response. | Async capabilities return a `jobId`; poll `GET /v1/jobs/{jobId}`. See [Jobs](/jobs). |
| **Artifact** | An output file from a job: a video, thumbnail, caption file or metadata. | When a job is `done`, URLs appear under `job.artifacts`. |

## Your brand and audience

| Term | Meaning | Where it comes from |
| - | - | - |
| **Brand Foundation** | Shared context and rules every Brand in the workspace inherits. | Configured in the dashboard. |
| **Brand** | One identity you publish as, with its own subject, voice, color, rules and products. | `POST /v1/brands`; use `brand.id`. |
| **Product** | Something your content may promote. | `POST /v1/products`; the response has both `id` (the record) and `productId` (the value Brands and autopilots refer to). |
| **Connected account** | A social account whose owner authorized Sigmora on the platform's own consent screen. | Connected in the dashboard. The API never accepts social passwords. |
| **Publish target** | The exact destination inside a connected account, such as one YouTube channel. | Selected in the dashboard. Generate without publishing by sending no destinations. |
| **Campaign** | A record that groups content for one launch or distribution effort. | `POST /v1/campaigns`, or created by an autopilot run. See [Campaigns](/campaigns). |

## Research and automation

| Term | Meaning | Where it comes from |
| - | - | - |
| **Theme** | A stable subject classification, such as Personal Finance. | `GET /v1/themes`; copy `themes[].id`. See [Themes](/themes). |
| **Trend** | A time-bound signal built from recently observed content. | `GET /v1/trends`; copy `trends[].id`. |
| **Discovery plan** | The platforms and search terms Sigmora watches for one Brand. | `PUT /v1/discovery/configs/{brandId}`. See [Niche discovery](/discovery). |
| **Autopilot** | A saved workflow that picks a trend, writes in a Brand's voice, makes a video and optionally publishes it. | `PUT /v1/autopilots/{brandId}`. See [Content autopilot](/autopilot). |

## Conventions

* **Ids are opaque.** Copy ids and cursors exactly as returned; do not parse or
  construct them. [Identifiers](/identifiers) lists where every id comes from.
* **Every response has `success`.** `true` with the result's fields on success;
  `false` with `code` and `error` on failure. See [Errors](/errors).
* **Availability is live.** `available: true` in `GET /v1/capabilities` is the
  only availability signal your integration needs.
* **Sigmora chooses providers.** Generation models, transcription services and
  other providers are picked for you unless a field explicitly asks for one.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.