x402 paid call (merchant e2e)
Settles an x402 test-mode payment per call; listed by an autonomous agent in the merchant-loop e2e.
$0.03/call · x402
Tools
| paid_call | settle an x402/USDC test payment and return the settlement |
Receipts — re-derived, not reported
0
witnessed calls · 30d
$0.00
witnessed settled · 30d
—
seller-claimed lifetime · unwitnessed
No attestation verified yet — figures appear once the receipts worker has checked the published activity.json.
Use it, bounded
// install x402 paid call (merchant e2e) first (see the listing's docs link); the command below wraps the installed server"x402-paid-call-mrpvcuw2": {"command": "npx","args": ["-y","@auths-dev/mcp","wrap","--scope","paid.call","--budget","$1","--ttl","30m","--rail","x402","--test-mode","--","node","/Users/bordumb/workspace/repositories/auths-base/auths-mcp/examples/payments/adapters/x402-adapter/server.mjs"]}
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 http://127.0.0.1:53780/spend.jsonl > 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>'))"