Before an agent acts, what gives it the right?
Understand one real-world situation. Then explore decisions, schema validation and reproducible technical artifacts.
A five-step case for any visitor; the technical Playground remains below.
See the nontechnical explanation → · I use AI with my team →A refund can be prepared. Who authorized its payment?
Follow one case from request to evidence. After that, use the Playground and the official schemas.
Try changing the authorized beneficiary:
Demonstration only. No keys, real payments, identity or institutional approval are checked.
From your idea to a first governed release.
Start with your product. Understand S and AI tracks and download the evidence you need, without a long institutional questionnaire.
Start the quickstart →INTEROPERABILITY · AP2 / OAUTHA valid signature does not grant legitimate authority.
See Ana’s $18,000 payment and why a cryptographic mandate cannot give the signer powers they do not hold.
Explore the story →Try it, validate, and inspect the contracts
No execution takes place. The Playground demonstrates fictional boundaries; the schema validator checks official JSON structure.
Synthetic scenarios
action.jsonauthority.jsonLocal SHA-256, not an immutable audit trail or conformance verification
Official JSON Schemas
Open the real 2026-11-08 machine package schemas. The editor only checks JSON syntax and does not certify conformance.
Check JSON syntax
Open the real 2026-11-08 machine package schemas. The editor only checks JSON syntax and does not certify conformance.
Reproducible conformance CF0–CF5
Vectors and runners are included from the official machine package for local execution.
| ID | What it tests | Vectors | File |
|---|
cd assets/machine/10_CONFORMANCE && python runner/run_conformance.pyRun the tests outside the browser; reference results are not an implementation certificate.
Integrate without fictional SDKs
The reference contract describes technology-neutral interfaces. The official OpenAPI uses a .invalid domain placeholder, not a live production endpoint.
Real technical source
Explore the case and capability vs authority.
Inspect the official machine-layer schemas and objects.
Run the CF0–CF5 conformance runners locally.
Integrate an enforcement point independent from the reasoning component, as required by C19.
OpenAPI 3.1
The reference contract describes technology-neutral interfaces. The official OpenAPI uses a .invalid domain placeholder, not a live production endpoint.
People behind the infrastructure
Explore how CAINCO teams designed three governed agents and why DAcorp adopted the approach internally.
Read real stories →