# Exalto Capture

> The flight recorder for your AI work. Capture your sessions on your machine, have a third party seal the ones you need to show, and let anyone verify them. The desktop app, the SDK and CLI, and the open protocol underneath.

You capture, Exalto Seal (or another notary) seals, anyone verifies. A sealed trace proves that the disclosed bytes traveled an authenticated connection with the named AI provider, that they have not changed since capture, and that the named notary witnessed them at the stated time. It does not prove who was at the keyboard, that every call was disclosed, that a local tool really ran, or that an answer was correct. Local capture is free, always. You pay for what you seal.

Every page below has a Markdown twin at the same address with `.md` added. The whole site in one file is https://capture.exalto.ai/llms-full.txt. The public command names are `capture` (the command client) and `captured` (the local service); the protocol is the Exalto Capture Protocol (ECP).

## Start here

- [For agents](https://capture.exalto.ai/docs/agents.md): the procedure for an agent with a shell, with the command and the JSON field that proves each step, the ask-before and never lists, client configuration, and the prompt.
- [Install options](https://capture.exalto.ai/docs/getting-started.md): the macOS app or the CLI and local service; the installer, the configuration file, provider routes for Claude Code, Codex, OpenAI, OpenRouter and DeepSeek, and finding local Traces.
- [Overview](https://capture.exalto.ai/docs.md): the workflow (capture, choose, seal, verify or share), the two evidence states, what is automatic, a first run.

## Understand

- [Trust model](https://capture.exalto.ai/docs/how-it-works.md): the exact provenance claim, who sees what, authenticated versus observed data, what the proof does not establish, how trust in a notary key is established.
- [Trace packages](https://capture.exalto.ai/docs/trace-packages.md): sealing, the `.llmtrace` package layout, offline verification with the CLI, the hosted verifier at `POST https://api.capture.exalto.ai/api/verify`, and the review-before-sharing boundary.
- [What it costs](https://capture.exalto.ai/docs/hosted-credits.md): capture is free, sealing is what you pay for, plans and balances live on the account.
- [Share a Trace](https://capture.exalto.ai/docs/share.md): deliberate upload of one sealed package, visibility, the upload boundary, admission checks.

## The site

- [Landing page](https://capture.exalto.ai/index.md): what Exalto Capture is, how it works, the quickstart, the components, applications, the trust model, and the prompt to hand to an agent.
- [The local service's OpenAPI contract](http://127.0.0.1:8788/openapi.json): published by a running `captured`; the authority for every route, field and status.
- [Install script](https://capture.exalto.ai/install.sh): `curl -fsSL https://capture.exalto.ai/install.sh | sh` installs `capture` and `captured` for Apple silicon macOS and Linux.
- [Public Runtime source](https://github.com/exalto-ai/capture-runtime): the protocol, daemon, CLI, generic notary, dashboard, updater and verifier.
- [Verify a trace](https://seal.exalto.ai/verify), [public traces](https://seal.exalto.ai/traces) and the [notary registry](https://seal.exalto.ai/registry) at Exalto Seal.

## Optional

- [Privacy](https://capture.exalto.ai/privacy.md) and [Terms](https://capture.exalto.ai/terms.md).
- [Proof of Thought](https://proof.exalto.ai/): the sibling product, a scratchpad for thinking and editing with AI that shows what you contributed and what the model did; its seals come from Exalto Seal.

Exalto Seal is not a notary public. Sealing is not a notarial act. A receipt is cryptographic evidence, not a legal instrument. The ECP specification uses "notary" as a technical role term, in the way public-key infrastructure uses "certificate authority."