Can it do that?
What does the record show?

1 · Before the action: permission.

The reference gate checks one proposed mutation against an explicit grant, scope and limits. Action Lab makes those decisions visible in a browser simulation. The public Check API checks replies; it does not issue a production grant or execute an action.

2 · After the action: inspect the evidence.

The reference issuer can bind a receipt to an attested mutation and a digest of its completion evidence. A proof bundle adds the signed checkpoint and inclusion proofs needed for local verification. The reference examples use fixture evidence and test keys, with production signing off.

The offline verifier checks the bundle against keys you choose. Valid signatures establish what those keys signed. They do not independently establish that an external provider completed the action. Read exactly what verification establishes.

3 · When it breaks: reproduce and keep the test.

Repair Lab replays an included failure and its bounded repair. MCP Chaos exercises documented faults against the included refund fixture. Download the example, inspect its assertions, and adapt the test to your own safe environment. A fixture passing is evidence about that fixture, not a guarantee about an arbitrary integration.

Use the same surfaces from your tools.

Start with the HTTP API or the hosted read-only MCP endpoint. Framework adapters are local source distributions. The agent manifest identifies current endpoints and availability; release evidence records their boundaries.