Agent reputation
Half of agent payment volume is fake. Reputation has to start from money that moved
Agent registries on Solana and Ethereum promise trust scores for AI agents. Ratings and raw volume are both easy to game. A scoring design built on settled payments from credible, unrelated counterparties.
PrizenLabs//3 min read/5 sources
- The problem
- Analysts found that roughly half of x402 transactions were wash trading or self-dealing, and star ratings are cheaper still to fake, so neither can safely gate money.
- Our proposal
- Score agents on net demand: settled stablecoin payments, with self-dealing and circular flows removed and each dollar weighted by the credibility of the wallet that paid it, published as a verifiable onchain account.
The Solana Agent Registry, built on the ERC-8004 Trustless Agents standard and interoperable with it on Ethereum, gives AI agents an onchain identity and a place to post and read reputation. Among its intended uses, Solana lists DeFi protocols open only to agents with verified reputation scores.
That use case lives or dies on one question: what is the score made of?
The problem: every cheap signal is gamed
Two signals are easy to collect, and both are easy to fake.
- Ratings. Feedback registries record what agents say about each other. A ring of agents controlled by one operator can rate each other perfectly at almost no cost.
- Payment volume. Money looks like a stronger signal, but analysts at Artemis found that roughly half of x402 transactions were self-dealing or wash trading, where funds cycle back to the seller. Different trackers report very different headline totals for the same months, which shows how much the method matters.
A score that gates a lending pool or a vault is a target. If it can be bought for the cost of transaction fees, it will be.
The proposal: score net demand, not activity
We built Agent Trust Oracle around one idea: the hardest thing to fake is money that real, unrelated counterparties paid for a service. The pipeline:
- 01Index settled payments only. x402 payments, payment-channel settlements and agent-wallet transfers, classified per rail and normalised to dollars. Ratings are not inputs.
- 02Resolve entities. Wallets that share a funder, a fee payer or a registry owner are clustered into one entity. Thirty fresh wallets funded by one address count as one customer.
- 03Cancel cycles. Value that flows from an agent through intermediaries and back is removed before anything is credited.
- 04Weight by credibility. A dollar from an aged wallet that pays many services counts fully. A dollar from a fresh, single-purpose wallet barely counts. Credibility propagates, in the spirit of TrustRank.
- 05Resist griefing. Unsolicited payments can never lower a score. Only an agent's own flows can penalise it.
- 06Publish verifiably. Each epoch commits a Merkle root of scores plus hashes of the method and inputs, so anyone can reproduce it.
In a synthetic economy, an honest agent with twenty repeat customers and $10 of revenue scores far above a wash ring that cycled $10,000, which scores zero.
Reading it from a program
Scores live in onchain accounts that any Solana program can read with a single account load and no cross-program call, so a vault can check an agent's trust in the same instruction that moves funds. Agents without a score account can present a Merkle proof instead. TypeScript clients read the same data free onchain or through a paid x402 API.
Open questions
- Cold start. New, honest agents have no history. Protocols should pair low score thresholds with small limits rather than shutting newcomers out.
- Identity silos. A score should read existing registries, ERC-8004 today and others later, rather than invent another.
- Method governance. A public method helps auditors and attackers alike. Committing hashes of the method each epoch keeps changes visible.
What to measure
- Raw versus credited volume. The gap between what an agent appears to earn and what the score credits. A large gap is the signal, not a problem.
- Entity count per agent. How many independent paying entities sit behind each score after clustering.
- Score stability. How much a score moves epoch to epoch without new real demand; jumpy scores are easy to game.
- Losses behind gated access. For a protocol that gates on the score, defaults and losses by score band over time.
How we would start
If you run a protocol that wants agent-only access, start by deciding what the score gates and how much value sits behind it, then set limits that grow with the score. If you run an agent marketplace, publish settled-payment data in a form an oracle can index. Both are part of our onchain AI agents and DeFi work, and they sit naturally beside the payment design in agent payments that settle on proof.
Sources
- 01Agent Trust Oracle: payment-grounded trust scores for Solana agents (GitHub)
- 02Solana: Agent Registry
- 03ERC-8004: Trustless Agents
- 04Forkast: half of x402's transaction volume is artificial
- 05The Defiant: Visa's Sheffield pegs adjusted x402 volume at $19M
Figures are as reported by the sources on the date above. Where sources disagreed, we say so in the text. Nothing here is legal or investment advice.