# Reference (/docs/reference)



Reference pages are for lookup, not learning. When you already know the concept
and just need the exact key, flag, code, endpoint, or term, this is where to
find it.

The public vocabulary — <Term name="Work" />, <Term name="Route" />,
<Term name="Settlement" /> — is a reading layer over stable API and domain names;
the [glossary](/docs/reference/glossary) carries the bridge from each primitive
to the type it maps onto (`Work` is a `Routable`, and so on). Reference pages use
the technical names, because that is what you type.

What lives here:

* **Configuration** — every `DUCTOR_*` variable and YAML key, per subsystem.
* **CLI** — every `ductor` subcommand, flag, and exit code.
* **Errors & status codes** — the stable error catalog and its wire mapping.
* **API surface** — how methods are served (ConnectRPC / gRPC / REST), the
  interceptor chain, versioning, rate limits, pagination, and health endpoints.
* **Glossary** — the vocabulary used across the docs and product.

<Cards>
  <Card title="Configuration" href="/docs/reference/configuration">
    Every `DUCTOR_*` environment variable and YAML key, grouped by subsystem,
    with types and defaults — including AI, MCP, entitlements, and BYOK.
  </Card>

  <Card title="CLI" href="/docs/reference/cli">
    Every `ductor` subcommand and its flags — serve, dev, migrate, schema,
    health, validate-config, workflow, and more, with exit codes.
  </Card>

  <Card title="Errors & status codes" href="/docs/reference/errors">
    The RFC 9457 Problem Details model, the stable error catalog, and the
    sentinel → Connect → HTTP mapping.
  </Card>

  <Card title="API surface" href="/docs/reference/api-surface">
    Tri-protocol serving, the external/internal plane split, the interceptor
    chain, versioning, rate limiting, pagination, and health endpoints.
  </Card>

  <Card title="API surface map" href="/docs/reference/api-surface-map">
    Find every API tag, its capability, and the narrative documentation that explains it.
  </Card>

  <Card title="Glossary" href="/docs/reference/glossary">
    The vocabulary — coordinator, pool, recipient, strategy, connector, MCP,
    entitlement, bridge, and more.
  </Card>
</Cards>