Open delivery receipts for x402 and paid HTTP APIs.
When a script or agent pays an HTTP endpoint via x402, an on-chain transfer log proves funds moved, while HTTP 200 delivers bytes over TLS. Once TLS terminates, nothing links the payment transaction to the response body that was actually returned.
Paxiom (paxiom.receipt.v0) is a free, MIT-licensed specification and reference toolkit that attaches an Ed25519-signed Payment-Receipt header (with X-Paxiom-Receipt backward compatibility) binding the canonicalized request, the SHA-256 digest of the delivered JSON or binary payload, the seller's published key identity, and the settlement reference so any buyer, wallet, or audit log can verify delivery independently.
Usage
Issuing receipts on the seller endpoint and verifying signatures, signer keys, and payload digests on the buyer require zero runtime dependencies and zero paid gatekeepers.
1. Issue on the seller endpoint (Node.js or Python)
// Auto-binds x402 v2 headers & signs Payment-Receipt
import { withPaxiomReceipt } from '@paxiom/receipts';
export default withPaxiomReceipt(paidHandler, {
privateKey: process.env.PAXIOM_PRIVATE_KEY_PEM,
issuer: {
name: 'acme-data',
uri: 'https://api.acme.dev',
keyId: 'seller-01'
},
serviceName: 'Orderbook Snapshot'
});
2. Pin seller keys, verify payload & check settlement
// Discover seller keys & verify offline import { discoverIssuerKeys, verifyResponseReceipt } from '@paxiom/receipts'; const keys = await discoverIssuerKeys('https://api.acme.dev'); const res = verifyResponseReceipt(httpRes, { output, expectedIssuerPublicKeys: keys.publicKeys, expectedPayTo: '0xSeller...' }); # Free public Base USDC settlement check: curl -sX POST https://api.paxiom.org/v1/receipt/verify-live \ -H 'content-type: application/json' \ -d '{"receipt": {...}, "output": {...}}'
Open SDKs & Free Public Reference Endpoints
| Surface | Access / License | Behavior |
|---|---|---|
@paxiom/receiptspaxiom-receipts |
Free (MIT) | Zero-dependency Node ≥18 and Python ≥3.10 SDKs for jcs-sha256 & raw-sha256 payload binding, Ed25519 signing, x402 v2 header parsing, key discovery, and offline verification. |
paxiom-receipt-mcp |
Free (MIT) | Local stdio MCP server and remote Streamable-HTTP endpoint (https://api.paxiom.org/mcp) exposing receipt and preflight tools to MCP clients. |
POST /v1/receipt/verify |
Free | Stateless hosted mirror of offline verification (schema, canonical base64, Ed25519 signature, signer authorization, expiry, and outputHash match). |
POST /v1/receipt/verify-live |
Free (60 req/min/IP) | Public reference verifier that queries Base Mainnet / Base Sepolia RPC logs to confirm the claimed USDC Transfer settled, returning a counter-signed Payment-Receipt. |
POST /v1/x402/preflight |
Free (30 req/min/IP) | Public pre-payment scanner that probes an unfamiliar 402 Payment Required endpoint to flag spoofed token contracts, redirect traps, or missing /.well-known/x402-keys.json / receipt support. |
Why Verification Is Not a Boolean
A seller holds their own signing key, so a valid seller signature alone cannot prove that the signer owns the paid endpoint or that a claimed transaction hash settled on-chain. Verifiers evaluate receipts in strict precedence order (all 16 states) so callers never mistake an unverified claim for confirmed delivery:
| State | Meaning |
|---|---|
verified |
Schema, Ed25519 signature, optional signer pinning, and outputHash match, and settlement is either not_required or counter-attested against a pinned verifier key in /.well-known/x402-keys.json. |
settlement_claimed_not_checked |
Seller signature and payload hash are intact, but the receipt cites an on-chain payment that has not yet been checked against chain logs. |
unauthorized_issuer |
Signature is mathematically valid, but the signing key is not in expectedIssuerPublicKeys (from the seller's /.well-known/x402-keys.json) or payTo mismatches expectedPayTo. |
output_hash_mismatch |
Signature is valid, but the delivered JSON or binary body does not match payload.delivery.outputHash (truncated, substituted, or mutated in transit). |
invalid_signature |
Ed25519 verification failed, keyId mismatched, or key/signature base64 was non-canonical. |
Open Standard & Ecosystem Governance
paxiom.receipt.v0, both reference SDKs, and the api.paxiom.org runtime are 100% open-source under the MIT license with zero paywalls or vendor lock-in — any facilitator, wallet, or gateway can self-host the verifier using its own keys. Paxiom is maintained by Driftbound Labs LLC; for x402 extension collaboration, multi-chain adapter feedback, or scoped verification engineering engagements, reach out via Contact (kyle@paxiom.org).