Gateway Nanopayments Primer
Circle Developer Notes / 0.002400 USDCreceipt evidence
0x73a7f2ca...4744c4
paid to creator0.002400USDC
local proof
Circle Developer Notes
This receipt binds a source payment to the answer that used it. The previous hash links it into the append-only attribution ledger.
receipt hash0x73a7f2cabb2ec2d196212fe8a41745c932d8005327046a32f16c862b2b4744c4
previous hash0x1ecf222f59d2ef67de20f74ca22c237a28eec4eb2870e7fa58d262fbd2aaa78a
query id0x4e2614245dc002ce
source idcircle-gateway-nano
creator wallet0x2222...2222
created at2026-06-21T13:36:28.264Z
payment resource/api/sources/circle-gateway-nano
query payment hashnot reader-paid
payerlocal proof
transactionpending settlement
FeeRouter splitnot FeeRouter-routed
FeeRouter createSplitnot FeeRouter-routed
FeeRouter paynot FeeRouter-routed
answer context
How can a budgeted AI agent buy publisher citations without overspending?
The paying agent treated "How can a budgeted AI agent buy publisher citations without overspending?" as a source-backed answer, not a free scrape. Circle Developer Notes: Circle Gateway batches signed EIP-3009 authorizations so x402 payments can clear at sub-cent values without per-payment gas. Indie Researcher: A source payment should be tiny, automatic, visible to the creator, and tied to the answer that reused the work. Forum Protocol: Forum-style mandates bound an agent budget, publish receipts, and make spend controls enforceable instead of advisory. It bought the minimum useful bundle of sources, paid each cited creator in USDC atomic units, and wrote a receipt chain that ties the answer to the citations that earned.
Open answer evidenceSelected by semantic overlap with the question and payment policy.