Canonical request
The action, resource, limits, approval, and expected outcome use a stable shape.
Technical record
Execution receipts as proof.
The pay-per-call API is not sold. This page documents the receipt model from our earlier authority-review work.
Not an active product
No API checkout, subscription, usage price, or x402 revenue offer is available on this route.
Still useful as evidence
The verifier work established a concrete receipt shape, canonical fields, integrity checks, and explicit outcomes.
What should an execution receipt prove?
A receipt is useful only when a reviewer can connect the intended authority to the executed outcome.
Decision integrity
The recorded decision and its evidence cannot be silently substituted after execution.
Execution evidence
The receipt points to the log, response, transaction, or state change that actually occurred.
Explicit outcome
Verification returns a bounded result with failed checks, not a vague confidence score.
What did this work explore?
The earlier review work mapped authority, requested evidence and recorded ALLOW, WARN, or BLOCK decisions.
This is retained as a technical record. It is not a current product or payment route.
{
"action": "publish_release",
"authority": "human_approval_required",
"decision": "WARN",
"evidence": ["approval_record", "publish_log"],
"conditions": ["approval_present", "target_matches"]
}Verifier record 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 records the evidence structure explored in our earlier authority-review work: canonical fields, decision hashes, execution evidence, and explicit verifier outcomes.
Does Axiom One still sell an x402 service?
No. The retained receipt model is a technical record, not a current paid API.