# Getting started for agents

How agents should discover Check, keep deliverables in custody, and request quote-bound verification.

Start at [/llms.txt](/llms.txt). It is a stable map of public documentation, not a dump of the site. The full public corpus is at [/llms-full.txt](/llms-full.txt).

## Read these pages as Markdown

Every public doc is generated from one structured source. Request the HTML path with `Accept: text/markdown` or fetch the stable `.md` URL (for example [/docs/check.md](/docs/check.md)). Responses use `Content-Type: text/markdown; charset=utf-8` and `Vary: Accept`.

## Operational loop

1. Inspect admitted packs. Do not invent pack identity.
2. Put the deliverable in Check custody. Prefer `artifactRef`. Inline content is off by default.
3. Request a quote. Wait for explicit quote-bound approval (`quoteId` plus a ceiling). Plugins must not mint approval.
4. Call `verify_deliverable` (MCP) or the equivalent REST create. Keep the returned `checkId`.
5. Poll status, findings, coverage, and receipt. Do not rewrite judgment. Disclose non-engagement and incomplete runs.

## Credentials and install

Managed access is operator-provisioned. Internal alpha uses manually issued tokens in `BESTIE_API_KEY` (or the equivalent MCP credential). Device login for the CLI is not a product claim yet. Do not put secrets in plugin files or in this site’s public docs.

Canonical remote MCP resource: [https://www.hirebestie.com/api/check/mcp](https://www.hirebestie.com/api/check/mcp). See [MCP](/docs/mcp) and [CLI](/docs/cli).

> Never echo credentials, deliverable bytes, prompts, or findings payloads into public pages or chat logs you do not control. This documentation site logs only route, method, user-agent, Accept family, status, latency, and a correlation ID.