Route Receipt v0.1

Route Receipt v0.1 defines a JSON document for the route that produced one AI response. A receipt can travel with an API response, live in an audit log, or render in a user-facing transparency panel.

Core receipt details

A conforming receipt records the receipt version, the response it describes, when it was issued, the provider, the served model, the requested model alias if one was used, and the disclosure view for which the receipt was generated.

The model fields separate the name requested by the caller from the model that actually served the response. If a provider only exposes a model family or alias, the receipt should use that rather than inventing a resolved version.

Route fields

The schema treats capability tier, tool calls, retrieval sources, fallback attempts, safety interventions, region scope, data-retention mode, and billing or latency class as optional fields because platforms expose these facts at different levels of precision.

Each optional field uses a status value when the exact fact cannot be disclosed. The expected statuses are exposed, redacted, not_exposed, not_applicable, and unknown for that field. A receipt should use an explicit redaction marker when a fact cannot be disclosed.

Redaction by view

A single event can produce different views. A user view may show the model family, tool category, and whether fallback occurred. An auditor view may include internal request identifiers, policy-rule identifiers, and more precise retention metadata.

Redaction marks a field as withheld. It shows that the fact exists and was withheld. That distinction matters when a team needs to know whether a missing value means “not applicable” or “known but intentionally hidden.”

What falls outside scope

Route Receipt leaves model evaluation, provider ranking, safety policy, and procurement policy to other systems. It also does not require providers to reveal private reasoning traces, router internals, safety-classifier prompts, exact failover thresholds, or infrastructure coordinates.

The schema captures only the route and leaves out a full provenance record. It sits near the answer and explains the route that served it.

Schema versions

The schema identifier is https://routereceipt.org/schemas/route-receipt/v0.1/schema.json. Subsequent versions follow semantic versioning, with additions remaining backward-compatible within a major version.

JSON Schema is the canonical v0.1 schema.