receipt evidence

0x225b5a73...c7b6c9

Back to Tollgate
creator amount0.001500USDC

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.

payment statusaccrued -> claimable on-chain
settlement modeforum-routed
amount0.001500 USDC
receipt hash0x225b5a73f6556c9751fd43a788a1cf8583960d201a841c920e27bb3017c7b6c9
previous hash0x75d8a51dfa465b5afcad00dfcd506c6f3508f53fa21628fe125581a896a6baf6
query id0xa6a768db36d99128
source idforum-mandates
creator wallet0x5555...5555
created at2026-06-24T14:47:35.512Z
payment resourceforum-fee-router:0xeff9bc359e8f2a5eabce55af3f1bb24f98eabf59
query payment hashnot reader-paid
payer0x4164F5B52ecc6F847f03071A287b0B59954cbcEe
FeeRouter split64
FeeRouter createSplit0x7e7b4977...8775ec
FeeRouter pay0x89f90d40...d3c179
contributorssingle recipient
canonical URLhttps://forum.gudman.xyz
content fetched atnot recorded
source content hashnot recorded
source excerpt hashnot recorded
ownership proofnot verified
ownership signernot verified

answer context

What parameters control how an AI agent decides to pay or refuse a knowledge source?

An AI agent's decision to pay or refuse a knowledge source is controlled by a **Spend Policy** with nine key parameters: (1) **max price per citation** — the ceiling price the agent will pay; (2) **min relevance score** — a threshold below which sources are rejected regardless of price; (3) **bonded-source requirement** — whether the source must post collateral or reputation; (4) **session cap** — total budget limit per research session; (5) **dedup window** — time period to avoid paying twice for the same content; (6) **receipt visibility** — whether payments must be on-chain and auditable; (7) **creator mandate** — whether the source creator has published spend controls the agent must honor; (8) **x402 protocol support** — whether the source accepts nanopayment settlement; and (9) **policy enforcement mode** — whether spend controls are advisory or hard-blocked. These parameters are typically expressed as a JSON policy document, but can also be generated from plain-English instructions using natural language policy builders. The agent evaluates each candidate source against this policy: if price exceeds max, relevance falls below threshold, or mandatory controls are violated, the source is refused; otherwise, the agent pays via on-chain USDC settlement on Arc with Circle Gateway x402, generating a verifiable receipt tied to the citation.

Open answer evidence

Covenant Account Spend Controls

Forum Protocol / 0.001500 USDC
Explains how creator-published mandates and spend controls become enforceable constraints that agents must respect when deciding to pay, adding the governance layer to policy parameters.No paid excerpt recorded.