Surfaces compared
The recipes use the HTTP API, the lowest-level surface and the one that always works. For many tasks another surface is shorter:Core offerings
Agents cookbook
Register an agent, give it tools, and record activity from an external runtime.
Publish and retrieve skills
Publish, find, retrieve, and inspect reusable skills through the API.
Publish logical model
Publish an ontology release and retrieve bounded context for agents.
Map ontology to physical data
Publish governed mappings from a release to your tables and columns.
Choose where to start
Each surface signs in differently: MCP clients use OAuth,
brain uses a token stored with brain auth login or read from REGISTRY_TOKEN_<NAME> in CI, atlanai SDK tracing reads an API key and workspace from the environment, and the SDK management client takes them as arguments. Every request acts as the authenticated identity, so it can create, change, or expose resources only in workspaces that identity can reach. Keep credentials in an approved secret store; see Authentication. The site does not send live requests or store credentials: run examples from an approved development or deployment environment.See also
- API quickstart: Verify your credential, workspace scope, and response shape first.
- Errors and retries: Recover from documented API failures without duplicating a write.