Auths Receipts

receipts invalid

Turn any settlement into a signed, offline-re-derivable evidence bundle with an anchored verdict — receipt_build, receipt_verify, dispute_evidence, evidence_export, reversal_determine. Nothing here is trusted: every answer re-derives from signed logs.

$0.05/call · x402 · docs

Tools

receipt_build	payment ref → signed EvidenceBundle (anchored as-of verdicts)
receipt_verify	bundle → re-checked as-of verdict, fully offline
dispute_evidence	the retainer-grade dispute bundle with freshness stamp
evidence_export	generic exhibit (pdf/text) with verification appendix
reversal_determine	remit-violation → signed reversal/v1 determination

Receipts — re-derived, not reported

witnessed calls · 30d

$0.00

witnessed settled · 30d

—

seller-claimed lifetime · unwitnessed

Signed activity attestation, verified against the seller's public identity registry (head 99b134b6a458…). Growth figures count only what this market witnessed — never the seller's claim.

Use it, bounded

// install Auths Receipts first (see the listing's docs link); the command below wraps the installed server
"auths-receipts": {
  "command": "npx",
  "args": [
    "-y",
    "@auths-dev/mcp",
    "wrap",
    "--scope",
    "paid.call",
    "--budget",
    "$1",
    "--ttl",
    "30m",
    "--rail",
    "x402",
    "--test-mode",
    "--",
    "auths-receipts-server"
  ]
}

The budget is yours: the gateway refuses any call that would cross it — usage-cap-exceeded — before this endpoint is ever invoked.

Test-mode uses sandbox rails — Stripe test + x402 base-sepolia. Without a funded wallet and facilitator it settles a recorded fixture, not an on-chain transaction: any tx hash you see is illustrative. To settle for real on base-sepolia, add --custody-credential + a facilitator URL (see the docs link on this listing).

Audit this yourself

The seller publishes a signed activity attestation (activity.json) — an aggregate committing to its private per-call log without revealing any counterparty. A party who never called this endpoint can re-check the signature and the market-witnessed growth, trusting neither the seller nor us:

curl -s https://raw.githubusercontent.com/auths-dev/receipts-activity/main/activity.json > activity.json
# verify the signed aggregate against the seller's public identity registry:
node -e "const s=require('@auths-dev/sdk');console.log(s.verifyActivityAttestation(require('fs').readFileSync('activity.json','utf8'),'<fetched registry dir>'))"