> ## Documentation Index > Fetch the complete documentation index at: https://www.agent37.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # AGENTS # AGENTS.md Guidance for AI agents working on the Agent37 docs. `CLAUDE.md` imports this file via `@AGENTS.md`, so this is the single source of truth — edit here, not there. ## About this project * The public documentation for **Agent37 Cloud**, built on [Mintlify](https://mintlify.com) and published at `https://www.agent37.com/docs`. * Pages are MDX files with YAML frontmatter; navigation, theme, and redirects live in `docs.json`. * Preview locally with `mint dev` (`npm i -g mint`); run `mint broken-links` before pushing. Publishing is automatic from `main` via the Mintlify app — there is no CI in this repo. * Mintlify auto-generates `llms.txt` and `llms-full.txt` at publish. **Customers' coding agents and our examples repo build clients straight from `…/docs/llms-full.txt`** — the reference is consumed as a spec, so precision beats prose. * For Mintlify product knowledge (components, configuration), install the Mintlify skill: `npx skills add https://mintlify.com/docs`. ## What the docs describe Two API planes, one `sk_live_` key — the navigation mirrors this split: * **Hosting API** (`https://api.agent37.com/v1`) — manage instances: instances, templates, exec, budgets, plus billing and errors reference. Takes the key as `Authorization: Bearer sk_live_...`. * **Agent API** (`https://{instanceId}.agent37.app/v1`) — talk to one instance's agent: chat (responses), streaming, sessions, files. Takes the same key raw, no Bearer prefix, as `X-Agent37-Key: sk_live_...`; `Authorization` passes through to the software inside the instance. Every sample on this plane must use `X-Agent37-Key`, never `Authorization: Bearer`. The API reference is **hand-authored MDX** — there is no OpenAPI spec to regenerate from. Endpoint pages use ``/`` and show curl, Python, and Node examples. If a page is renamed or moved, add a redirect in `docs.json` so old URLs keep working (several exist already). ## Accuracy rules * The platform is pre-launch and moves fast; the implementation is the source of truth and these docs are hand-written, so drift is the failure mode. **Verify behavior against the live API before documenting it** — never document from memory or from an example app. * An API change and its docs change ship together. "Update the docs later" is how the reference rots. * Pricing, limits, ids, and resource shapes in the docs are load-bearing — they're quoted to customers and parsed by coding agents. Change them only to match a real platform change. ## Image tags in docs Platform images publish weekly to GHCR (immutable dated tags like `2026.07.02b`, never republished, plus a moving `latest`). The docs must never require a weekly edit to stay correct: * **Never hardcode a dated tag as guidance.** The two non-rotting sources for "the current version" are the tag in a system template's `image_ref` on `GET /v1/templates`, and the GHCR package pages — link those instead (`https://github.com/orgs/agent37-platform/packages/container/package/`). * **Dockerfile `FROM` examples use `:latest`**, with the one mental model stated nearby: a built image freezes its base at build time, the FROM tag only matters at rebuild, pin a dated tag for reproducible rebuilds. * **Runnable request examples use `` placeholders** (`agent37-hermes@`, `ghcr.io/you/my-agent:`) — a copy-pasted placeholder fails loudly; a copy-pasted old tag silently pins an ancient release. * **JSON response examples show a real dated tag for realism; it is illustrative.** An old immutable tag is never wrong, just old — normalize opportunistically when editing a page, never as a release chore. Keep one consistent tag across all response examples when you do touch them. ## Terminology Use these exactly; consistent terms are what make `llms-full.txt` usable as a spec. * **Agent37 Cloud** — the product. **Workspace** — the account/billing unit; owns API keys and one **wallet**. * **Instance** — an agent's always-on computer at `https://{instanceId}.agent37.app`. **Session** — one conversation on an instance. **Response** — one agentic turn within a session. * **Agent** vs **model**: the agent is the software running on the instance (Hermes and OpenClaw today; Claude Code and Codex coming soon); the model is the LLM chosen per turn (`model` + `provider`). * **Template** — names the image an instance runs and can set its `default_port`; every other port URL is derivable and needs no declaration. **Gateway** — serves the Agent API inside the instance. * **Instance URL** — an instance's base address, `https://{instanceId}.agent37.app` (the default port, where the agent's API lives). **Preview URL** — a non-default port's address, `https://{instanceId}-{port}.agent37.app`, where a service or UI on that port is reachable. **Signed URL** — a time-boxed, tokenized form of either, mintable via `POST /v1/instances/{id}/signed-url`, that a browser can open without a header. * Billing: **wallet** (workspace money), **budget** (per-instance managed-spend cap plus **top-up** headroom), **managed services** (LLM / search / Composio through built-in credentials), **micros** (USD × 1,000,000), **past due** (renewal failed; instance force-stopped until a funded start). * Conventions: instance ids are 10-char lowercase alphanumeric; session/response ids are 32-char hex; Hosting API timestamps are epoch **seconds**, Agent API timestamps epoch **milliseconds**; list endpoints wrap results in `{ "data": [...] }`, newest first. ## Content boundaries * Document **only the two public planes**. The dashboard, internal/admin APIs, and fleet/host architecture are out of scope. * The OpenClaw setup guides (`openclaw/`, `channels/`, `models/`, `runtime/`, `networking/`, `tailscale/`) are intentionally hidden from the nav but searchable — they serve existing OpenClaw customers. Don't surface them in the Agents API nav and don't delete them. * The system template catalog has three entries: `agent37-hermes`, `agent37-hermes-small`, and `agent37-openclaw`. Claude Code and Codex are coming soon — mention them as coming, never as available. * Drafts go in `drafts/` or `*.draft.mdx` (ignored via `.mintignore`). ## Style * Active voice, second person ("you"); one idea per sentence; sentence case for headings. * Bold for UI elements: Click **Settings**. Code formatting for file names, commands, paths, endpoints, and field names. * Lead with the goal; prefer a runnable example over describing one.