JSON schemas
Each file in schemas/ is served unchanged at /docs/schemas/<name>.json.
KATA ActionConceptual schema for a proposed agent action submitted to KATA for pre-execution evaluation, including price integrity and the counterparty. Status: Concept / Open Design — not production ready.KATA AgentConceptual schema for an AI agent's identity and provenance within the KATA framework. Status: Concept / Open Design — not production ready.KATA Intent AgreementLifecycle record for the live intents inside a delegation: proposal, clarification, acceptance, acknowledgement, amendment, added intents, revocation, and expiry. KATA holds the spend ledger on this record. The event log is an audit trail. It is not, by itself, a revocation status service. Status: Concept / Open Design — not production ready.KATA DecisionConceptual schema for a KATA trust decision returned by POST /kata/evaluate. Reason codes include price-integrity labels. Status: Concept / Open Design — not production ready.KATA DelegationConceptual schema for a machine-readable delegation between a principal and an AI agent. Status: Concept / Open Design — not production ready.KATA institution keysKey document an institution publishes at https://<domain>/.well-known/kata-keys.json. KATA also keeps an allowlist. A rotated key stays trusted until not_after plus the grace period. The default grace is 7 days. Status: Concept / Open Design — not production ready.KATA Intent MandateImmutable signed intent bound to one agent key. The principal's signature covers the intent, the limits, the human-readable rendering, and the agent key. Status: Concept / Open Design — not production ready. The agreement record that carries this mandate is schemas/agreement.json. amounts stay major units, as in schemas/intent.json.KATA IntentConceptual schema for structured, machine-readable intent declared by a principal, including optional price and counterparty constraints. Status: Concept / Open Design — not production ready.KATA transparency log tree headSigned Merkle tree head for the append-only log of agreements and revocations. The JWS typ is kata-tree-head+jws. Entries are hash-chained and the root is a binary Merkle root. Status: Concept / Open Design — not production ready.