AgentReceipts live Alpha

How the proof path works.

AgentReceipts defines the permitted scope before an action, records the result afterward, and exposes a receipt that can be inspected and verified.

01See a recorded receipt flow Verify a sample receipt Technical JSON Open the machine contract

Alpha / static sandbox / entitlement fixture / non-settlement

Controlled action path
AgentReceipts controlled action path An agent crosses an allowed boundary to create an action receipt and verification result. A boundary failure routes to stop. AGENTBOUNDARYACTIONRECEIPTVERIFYSTOP / HOLD
Allowed pathBoundary failure

Action recognition

An agent is about to create an external effect.

Issue a refundSubmit a formChange a settingCall a service

Before, during and after

A controlled path from mandate to receipt.

The declared scope governs the action. The resulting record makes the path inspectable.

  1. 01 / BeforeMandate and proposed actionScope and intent are recorded before execution.
  2. 02 / DuringAction inside the boundaryThe declared rule determines whether execution continues.
  3. 03 / AfterAction receipt and verificationThe resulting record can be inspected and checked.

Authority boundary: AgentReceipts records the permitted scope. It does not independently grant authority or prove an external outcome.

See the seven-step technical flow
  1. 01
    Discover contractRead the public decision and tool routes.
  2. 02
    Identify mandate and intentState delegated authority and the proposed action.
  3. 03
    Select tool or templateChoose a supported public contract.
  4. 04
    Execute within boundaryProceed only inside the established authorization boundary.
  5. 05
    Produce receiptRecord the action result and linkage.
  6. 06
    VerifyCheck receipt identifiers, state, and checksum shape.
  7. 07
    Optional metadata-only telemetrySignal explicitly when useful; no hidden telemetry or raw payloads.

Decision boundary

Determine the safe next step before action.

The decision is explicit: continue, verify, do nothing, or stop.

Use AgentReceipts

External effectSpend, submit, change, authorize, or trigger another system.
Delegated authorityA mandate must be established before action.
Durable recordA receipt or machine-readable evidence is required.

Do not use AgentReceipts

Informational onlyNo external action or durable record is needed.
Unsupported requestThe action class or required fields are incomplete.
Authority unavailableThe required mandate cannot be established.
Fail closed: if authority, action class, or required fields cannot be established, stop. Agentic 402 here is a sandbox entitlement pattern, not payment execution or settlement.
Inspect the five controlled decision classes
AGENTIC 402 ACTIONcall_agentreceipts
DELEGATED CONSEQUENTIAL ACTIONcall_agentreceipts
EXISTING RECEIPT VERIFICATIONverify_existing_receipt
INFORMATIONAL NON-CONSEQUENTIALdo_not_call
UNSUPPORTED OR MALFORMEDfail_closed
Open controlled scenario fixtures

Receipt and verification

The artifact and its proof boundary.

Stable object names make the action lifecycle clear.

BEFOREMandate
BEFOREProposed action
AFTERAction receipt
AFTERVerification result
OPTIONALMetadata-only signal

Verification confirms

Identifiers, recorded linkage, declared state, checksum shape, and a reproducible result.

Verification does not confirm

External outcome truth, identity assurance, legal validity, financial execution, or settlement finality.

Choose a next action

Move from understanding to integration.

UNDERSTAND

See the controlled proof flow

Follow a recorded example from mandate to receipt.

Open the walkthrough VERIFY

Verify a sample receipt

Inspect what the verification result confirms and excludes.

Open verification CONNECT

Connect an agent or integration

Use the public machine contracts to select the safe path.

See machine contracts
FOR AN AGENT OR INTEGRATION

Machine-readable entry points

 Technical JSON

Public machine contracts are listed below. Private runtime inputs remain outside this surface.