Covenant Account Spend Controls
Forum Protocol / 0.001500 USDCreceipt evidence
0x41b05f2f...e554e1
accrued -> claimable on-chain
Forum Protocol
This receipt binds a source payment to the answer that used it; FeeRouter-routed receipts accrue into creator-claimable balances. The previous hash links it into the append-only attribution ledger.
answer context
How should an AI agent configure its spend policy for citation markets?
An AI agent should configure its spend policy for citation markets by: (1) setting enforceable budget bounds using mandate-style spend controls that publish receipts and make limits binding rather than advisory; (2) choosing a settlement layer (Arc with USDC) that supports sub-second finality and nanopayment batching to keep per-citation costs below one cent; (3) defining policy parameters including max price per citation, minimum relevance thresholds, bonded-source requirements, session caps, and deduplication windows—ideally via natural language conversion rather than manual JSON; (4) routing payments through x402-compatible gateways (Circle Gateway) that batch signed authorizations to avoid per-payment gas costs; (5) ensuring every citation payment generates an on-chain receipt with content integrity proof and SHA-256 evidence hash for transparency and creator visibility; and (6) using an MCP-compatible interface so the agent can call citation queries natively without custom integration. The policy should be tiny, automatic, visible to creators, and tied directly to the answer that reused their work.
Open answer evidence