# For agents These files let a coding agent set up a customer without a person reading a page. Hangar serves every file from Sydney, with no other origin involved. | Path | Type | What the file is | |---|---|---| | `/docs/index.json` | `application/json` | The index of the customer documentation: title, path and owning slice for each page | | `/docs/{page}.md` | `text/markdown` | The Markdown source of one docs page, for example `/docs/quickstart.md` | | `/api/openapi.json` | `application/json` | The OpenAPI 3.1 document for the `/v1` API, generated from the route table | | `/keyset.cbor` | `application/cbor` | The published key set that job certificates verify against | | `/keys.json` | `application/json` | The published key set, as JSON | | `/log/treeheads.json` | `application/json` | Every signed tree head of the log | | `/c/{id}/bytes` | `application/cbor` | A published job certificate in its canonical CBOR | | `/c/{id}/keyset` | `application/cbor` | The key set a published certificate verifies against | | `/hangar_cert.wasm` | `application/wasm` | The verifier compiled to WebAssembly, as the browser verifier loads it | | `/.well-known/security.txt` | `text/plain` | How to report a vulnerability (RFC 9116) | ## How to use them 1. Read `/docs/index.json` to find the page for the task, then fetch its Markdown with `/docs/{page}.md`. 2. Use `/api/openapi.json` for every call to the API. Send an `Idempotency-Key` header with every call that changes data. 3. Verify a certificate with `hangar verify `. The command runs offline. The same check runs in a browser at `/verify`. ## The read-only token for operator agents An agent that works for a TALOS Defence operator reads the operator plane with a read-only token: [The operator plane](operator_plane.md#the-read-only-token-for-agents) describes it. ## Related pages - [The verifier](the_verifier.md) - [What a certificate proves](what_a_certificate_proves.md) - [Jobs and the API](runs_and_the_api.md)