Arc Settlement Sketch
Arc Builder Desk / 0.002200 USDCreceipt evidence
0x700f0c1a...03456d
paid to creator0.002200USDC
forum routed
Arc Builder Desk
This receipt binds a source payment to the answer that used it. The previous hash links it into the append-only attribution ledger.
receipt hash0x700f0c1a343b194c61a325042ad609202f347038e52b7f10bc9007a66c03456d
previous hash0x724e46409b0400b6784f489148e6b7cd0fdbb37b3c3560f503c78c826120893d
query id0x9f6f708c0e24bf60
source idarc-finality-usdc
creator wallet0x3333...3333
created at2026-06-23T13:37:27.748Z
payment resourceforum-fee-router:0xeff9bc359e8f2a5eabce55af3f1bb24f98eabf59
query payment hashnot reader-paid
payer0x4164F5B52ecc6F847f03071A287b0B59954cbcEe
transaction0xb81f5010...c4a73b
FeeRouter split8
FeeRouter createSplit0x23bda0c6...814ee4
FeeRouter pay0xb81f5010...c4a73b
answer context
What does an agent need to settle nanopayments to creators on Arc, and how does budgeting work?
To settle nanopayments to creators on Arc, an agent needs: (1) USDC stablecoin for gas and settlement, (2) x402 payment protocol support for sub-cent value transfers, (3) batching infrastructure (like Circle Gateway's EIP-3009 authorizations) to avoid per-payment gas costs, and (4) Arc's app kits for payment workflows with sub-second finality. For budgeting, agents use covenant-style spend controls (like Forum mandates) that bind the agent budget, publish receipts, and make spend enforcement enforceable rather than advisory. Payment amounts should be tiny, automatic, visible to creators, and tied to the specific answer or citation that reused their work.
Open answer evidenceDirectly answers Arc settlement requirements: USDC stablecoin, sub-second finality, and app kits for payment workflows. Core to the infrastructure question.