Axiom One

Technical record

Execution receipts as proof.

The pay-per-call API is not sold. This page documents the receipt model behind our current authority reviews.

Is the verifier an active product?

No. There is no API checkout, subscription, usage price, or x402 revenue offer on this route. The page remains as a technical record of a receipt model and its limits.

What should an execution receipt prove?

A useful receipt connects intended authority to the executed outcome. It records a canonical request, decision integrity, execution evidence, and an explicit bounded result with failed checks.

How is this used now?

Proof Packs apply the same discipline when they map authority, request evidence, test conditions, and issue ALLOW, WARN, or BLOCK. x402 can be reviewed when a client already uses it, but it is not an Axiom One revenue line.

Questions

Is the Execution Receipt Verifier sold as an API?

No. The pay-per-call verifier is not an active product. This page is retained as a technical record of the receipt model and its limits.

Why keep the verifier page?

It shows the evidence structure behind our authority reviews: canonical fields, decision hashes, execution evidence, and explicit verifier outcomes.

Does Axiom One still sell an x402 service?

No. x402 is not an Axiom One revenue line. We can still review x402 as one payment mechanism inside a bounded Proof Pack when a client already uses it.

What should a team buy instead?

Choose the MCP Tool Authority Review Kit for a self-serve first pass, or a Proof Pack for a signed review of one real agent flow.