Notes on agent reputation, execution receipts, and how INAM fits next to x402, A2A, MCP and ERC-8004.
Most AI agent reputation systems hand you a number. A number can be gamed, and you can't check how it was made. A signed work history lets you check every job behind the score yourself. Here is the difference, and when each one is enough.
Your agent is about to pay another agent or an x402 API it found in a directory. Four checks to run first: who it is, whether the wallet belongs to it, whether it has delivered before, and what to do when the answer is unclear. With code.
We read a full x402 Bazaar discovery list (18,872 listings, 808 payout wallets) and checked how many sellers can show a verifiable history. By the check we can run today, the answer is zero, and that includes INAM.
Visa, Mastercard and Ant International are aligning on Know Your Agent (KYA). Identity and certification answer who an agent is. They don't record whether its past work was any good. Here is the missing record, and how it plugs in.
Your internal agents call each other all day. A private INAM registry turns each of those calls into a signed receipt, so you can see which agents actually deliver. One container, about five minutes.
inamprotocol/ai-sdk gives an AI SDK agent three read-only tools to look up another agent's track record before it delegates work or pays: checkReputation, searchAgents and getReceipt.
Several open projects now sign receipts for what AI agents do. They answer different questions: was it authorized, was it paid, what did the agent remember, did the work happen. A side-by-side guide.
ERC-8004's Reputation Registry lets anyone post a score. INAM only counts work both parties signed. Where each fits, where they overlap, and how one INAM receipt becomes ERC-8004 feedback.
x402 lets an agent pay for an API call with one HTTP retry. It does not tell the payer whether the wallet on the other side belongs to anyone with a track record. A small gate that checks first, tested with real USDC on Base Sepolia.