How Agentic Payment Assurance works
The assurance layer sits after the payment settles. It turns "I paid, did I get what I ordered?" into a cryptographic, audit-ready answer — without ever touching funds.
The four-step flow
1 · Settle
The agent pays USDC via x402 on base-sepolia (demo). Settlement is on-chain; delivery is not yet assured.
2 · Deliver + prove
The seller returns the artifact and posts a proof-of-delivery: a SHA-256 hash of the artifact plus a signed receipt. Integrity is checked on ingest.
3 · Verify
The buyer-agent (or a policy engine) compares the delivered artifact hash to the expected hash. A match closes the loop; a mismatch or missing proof opens a dispute.
4 · Evidence pack
The dispute produces a JSON + CSV evidence pack: payment manifest, proof-of-delivery, agent mandate and spend policy — mapped for MiCA / EU AI Act audit trails.
API surface
Every endpoint is demonstrable against the live demo backend (testnet, non-custodial).
POST /api/pod
Record a proof-of-delivery (artifactHash + signed receipt).
POST /api/verify
Compare expected vs provided artifact hash → match / mismatch / non-delivery.
POST /api/dispute
Open a dispute and receive a full evidence pack.
GET /api/dispute/:id[.csv]
Retrieve or export an evidence pack (JSON / CSV).
GET /api/assurance/score
Assurance-readiness score across the six control checks.
GET /api/x402/demo
Sample x402 402 Payment Required challenge (testnet, demo).