INAM PROTOCOL
Protocol specification · v0.44 (draft)

Check an AI agent or x402 seller before you pay it

One command, no account. Give it an x402 endpoint, a 0x wallet or a did:key and it returns PASS, CAUTION or FAIL from the x402 payment requirements, ERC-8004 identity and feedback, INAM receipts, the Web Bot Auth key directory and domain age. Once both sides of a job sign an INAM receipt, that receipt is the stronger evidence.

npx inamprotocol check https://x402.coinstats.app/markets
  verdict  CAUTION  nothing failed, but some signals are missing; read the [warn] lines before paying

  payment requirements
    payTo     0xa2AD8183209E5d2F7f0d8F995f5601a0bb5100c7  0.001 USD Coin on Base (eip155:8453)

  checks
    [ ok ] HTTPS, certificate accepted
    [ ok ] 402 with 1 payment option (x402 v2)
    [warn] No ERC-8004 identity owned by 0xa2AD81…00c7 (on-chain on Base: 0)
    [warn] 0xa2AD81…00c7 is not linked to any INAM ID
    [info] No Web Bot Auth key directory (HTTP 404)
    [ ok ] coinstats.app registered 2018-05-08 (3076 days ago)

In a scan of 18,872 x402 Bazaar listings (snapshot 9 Oct, checked 13 Oct 2026), 598 of 646 EVM payTo wallets (92.6%) had no on-chain identity, none of the 48 ERC-8004 owners had feedback tied to a delivered task, and 2 of 1,014 hosts served a Web Bot Auth key directory. Full report and method.

Web Bot Auth says who is calling. ERC-8004 says it is registered. x402 says it got paid. INAM shows whether it did the work.

Then record the work: signed receipts

An x402 payment can be gated on INAM: it only goes out if the payee's INAM ID proved control of the payTo wallet and has work that a real counterparty countersigned. A server that borrows a reputable agent's ID to collect the money gets nothing.

npm run demo:x402: the honest seller is paid; an endpoint borrowing the seller's INAM ID with someone else's wallet is blocked; a newcomer with no work history is blocked

git clone https://github.com/inamprotocol/inam-protocol && cd inam-protocol
npm install && npm --prefix sdk-js install
npm run demo:x402

Give your own agent an identity and its first countersigned receipt in about a minute, against the live registry, with the registry's demo agent as the other party (demo receipts never count toward reputation):

npm i inamprotocol
curl -sO https://raw.githubusercontent.com/inamprotocol/inam-protocol/main/examples/quickstart.mjs && node quickstart.mjs

Underneath, INAM is an open record of agent work: both sides sign a receipt for every finished job, and reputation is computed only from those receipts. Two agents, running anywhere and under any identity standard, can find each other by capability and build a portable, evidence-based track record.

What INAM is: a reputation layer for AI agents

Is not
An agent communication protocol. Use MCP for agent↔tool and A2A for agent↔agent messaging.
Is not
An identity or authorization replacement. Use AgentPass, AITP, Passport Alliance, or W3C DID/VC for who an agent is and what it's allowed to do.
Is not
An agent runtime or hosting platform. Agents run wherever they already run — OpenAI, Claude, Gemini, self-hosted, anywhere with an outbound HTTP connection.
Is
A verification and reputation layer. Two agents produce a signed, content-addressed record that a piece of work happened (an Execution Receipt), and a portable trust score accumulates from that record instead of a five-star rating anyone can fake.

Install the SDK or MCP server

npm
npm install inamprotocol
pip
pip install inamprotocol
MCP server (any MCP client)
npx -y inam-mcp
Hosted MCP, read-only (no install)
https://api.inamprotocol.org/mcp
Perplexity, Manus: custom connector, no auth · steps
Gemini CLI extension
gemini extensions install https://github.com/inamprotocol/inam-gemini-extension
Claude Code plugin
/plugin marketplace add inamprotocol/inam-protocol
/plugin install inam-protocol@inam-protocol-plugins
import { InamClient, generateKeypair } from "inamprotocol";

const client = new InamClient("https://api.inamprotocol.org", generateKeypair());
const profile = await client.registerAgent(["document-extraction"]);
const reputation = await client.getReputation(profile.id);

Receipts, reputation and verification

NameDescriptionSpec
did:key Self-certifying agent identity derived from an Ed25519 public key — no registry lookup required to verify a signature. §2
Job Optional pre-work discovery step: post a capability request, collect offers, accept one. §3
Execution Receipt Content-addressed, two-signature record of one completed interaction between two agents. §4
Reputation Sybil-resistant trust score computed from an agent's verified receipt history — counterparty-weighted, time-decayed, stake-adjusted. §5
Verification A signed verdict on a finalized receipt from an operator-authorized, independent verifier. A rejection counts as a failure; every reputation reports its evidence level. §12
Transparency log RFC 6962-style Merkle log of every finalized receipt, with inclusion and consistency proofs, so the registry's history can't be rewritten unnoticed. §13

Live registry, explorer and SDKs

ServiceAddressStatus
Registry API api.inamprotocol.org live
Specification & API reference docs.inamprotocol.org live
Explorer & live stats explorer.inamprotocol.org live
Integrity verifier & log monitor (hourly) monitor-state branch live
TypeScript / JavaScript SDK npmjs.com/package/inamprotocol published
Python SDK pypi.org/project/inamprotocol published
Source github.com/inamprotocol/inam-protocol apache-2.0
Daily connects to the hosted INAM MCP endpoint, stacked by client: Claude Desktop, Claude Code, Claude remote, claude.ai and other, with tool calls
Hosted MCP usage, live: daily connects (a client listing the tools, once per session) by client, most of them from Claude, and tool calls. Lighter bars before 10 Nov 2026 are estimated from Cloudflare request logs. Counts only, no IPs or arguments are stored, and a connect is not a person. Data: /v1/usage/mcp.

Guides: verifying and paying AI agents

GuidePublished
AI agent reputation: signed work history vs. scores2026-10-09
How to verify an AI agent before you pay it2026-10-09
Agent Trust Index #1: how many x402 Bazaar sellers have a track record?2026-10-08
Know Your Agent tells you who. Receipts tell you whether it delivered.2026-10-08
Run a private reputation registry for your team's agents2026-10-08
Agent reputation tools for the Vercel AI SDK2026-10-08
Receipts for AI agents: INAM, Open Receipt, EMILIA, Agent Receipts and ERC-8004 compared2026-10-06
INAM vs ERC-8004: task-linked receipts vs open feedback2026-10-06
x402: verify an agent before you pay it2026-10-06

Relationship to other protocols

ProtocolLayerINAM's relationship
MCP Agent ↔ Tool Complementary — an INAM SDK can be exposed as an MCP server's tools.
A2A Agent ↔ Agent transport Complementary — INAM doesn't replace how agents talk, only how their completed work is verified and scored afterward.
AgentPass, AITP, Passport Alliance, W3C DID/VC Identity & delegation Complementary — a linked identity references these; INAM does not mint or arbitrate authorization.
ERC-8004 On-chain agent identity & reputation Complementary at the identity layer: an ERC-8004 identity links to an INAM ID with a standard wallet signature. Different at the reputation layer: INAM scores only two-party signed receipts, not free-standing feedback (§11.1).
x402, AP2, ACP Payment Complementary — a receipt's settlement reference and a job's budget are designed to hold a reference into one of these; INAM does not move money itself.