# Azoth OS documentation

Azoth sits between your applications and the model providers. Every call answers three questions: who answers for it (the mandate), what it may do and under which law (the rule), and how a third party can check it (the proof).

## Mandate · Rule · Proof

- [Mandate](https://www.azothos.ai/docs/mandates) — Who answers for each AI use: systems with a named accountable person, a purpose and an end; agents with versioned mandates; the uses no mandate covers yet.
- [Rule](https://www.azothos.ai/docs/rules) — What a call may do, checked at the gateway before the model: policy rules, budgets, the applicable law, human approvals, the emergency stop.
- [Proof](https://www.azothos.ai/docs/proof) — What was decided, sealed in a hash-chained journal, signed in a receipt on every answer that is not streamed, exported as dossiers anyone can verify offline.

## Build and run

- [Quick start](https://www.azothos.ai/docs/quickstart) — Send your first governed call, keep its receipt, find its sealed decision.
- [SDK & CLI](https://www.azothos.ai/docs/sdk) — The SDK, the CLI with azoth proxy and the commit hook, MCP and the v1 REST API.
- [Enrichments](https://www.azothos.ai/docs/enrichments) — Costs and savings, model routing, the semantic cache, prompts, energy, the model catalog, the AI footprint in code.
- [Integrations](https://www.azothos.ai/docs/webhooks) — Governance webhooks, Slack, Microsoft Teams, PagerDuty and the GitHub App.
- [Self-hosted and air-gapped](https://www.azothos.ai/docs/self-hosting) — One image for every deployment, a Helm chart, a signed offline bundle.
- [Changelog](https://www.azothos.ai/changelog) — What changed, release by release.

**Need help?** — Email [hello@azothos.ai](mailto:hello@azothos.ai). Signed in to Azoth? Help, in your dashboard, answers first and writes to support with your context.

[GitHub ↗](https://github.com/azothos/azoth-verifier)
