identity · Listed · Found · 4 endpoints · Gateway-eligible
Agent Trust Lookup
Agent Trust Lookup
Know your agent before you serve it: wallet history and micro-payment behaviour on Base, ERC-8004 identity and feedback, Web Bot Auth and agent-card presence on
Indexed from this operator's public /.well-known/x402.json. Found is not operator-owned and is not attested. Claim or opt out.
Agent Read · Cleared Index
ROUTE
Route when you need identity at published x402 prices.
confidence
78%
source
signal
Index before you pay. Same payload for agents:
GET /api/cleared/agent-read?slug=agent-trust-lookup-a9nj
When to call
- Need identity via x402 and want Cleared-indexed payTo with a live scorecard.
- Budget between $0.005000 and $0.010000 per call on published endpoints.
- Know your agent before you serve it: wallet history and micro-payment behaviour on Base, ERC-8004 identity and feedback, Web Bot Auth and agent-card presence on
Risks
- Found — not operator-owned; claim status unknown.
- No Cleared settlement receipt on file yet.
- No Gateway traffic yet — market share unproven.
Price posture
Published 4 endpoints from $0.005000 to $0.010000.
Category · Gateway
identity · no Gateway routes yet — early / unproven on Cleared market share.
Endpoint hints
GET /v1/walletWho is this agent wallet? For sellers and marketplaces deciding whether to serve, rate-limit or extend credit to a buyer. Base activity (transactions, recent US
GET /v1/agentERC-8004 agent by id on Base: owner, verified agent wallet, registration URI and its resolved JSON (name, endpoints, skills), feedback count and average from th
GET /v1/domainAgent-readiness and identity profile of a domain: Web Bot Auth key directory (RFC 9421), A2A agent card (name, skills, extensions), MCP well-known manifest, llm
POST /v1/verify-requestVerifies a Web Bot Auth signed HTTP request (RFC 9421 HTTP Message Signatures) against the signer's public key directory: pass the request method, URL and the S
Evidence (Cleared)
- → Intake verified · Gateway-eligible
- → Trust 70/100 · pass · tier listed
- → Protocol mpp
- → Manifest reachable · schema valid
- → Found listing — indexed from public x402.json, not operator-attested.
Endpoints
Who is this agent wallet? For sellers and marketplaces deciding whether to serve, rate-limit or extend credit to a buyer
$0.010000GET https://agent-trust.agent-utils.workers.dev/v1/walletWho is this agent wallet? For sellers and marketplaces deciding whether to serve, rate-limit or extend credit to a buyer. Base activity (transactions, recent USDC transfers, micro-payment behaviour, distinct counterparties, USDC balance, ENS/Basename), ERC-8004 agent identities it owns with on-chain feedback, and a 0-100 trust score with tier and recommendations.
ERC-8004 agent by id on Base: owner, verified agent wallet, registration URI and its resolved JSON (name, endpoints, skills), feedback count and average from the Reputation Registry, distinct clients and the latest feedback entries
$0.010000GET https://agent-trust.agent-utils.workers.dev/v1/agentERC-8004 agent by id on Base: owner, verified agent wallet, registration URI and its resolved JSON (name, endpoints, skills), feedback count and average from the Reputation Registry, distinct clients and the latest feedback entries. Use to vet a counterparty agent before hiring or paying it.
Agent-readiness and identity profile of a domain: Web Bot Auth key directory (RFC 9421), A2A agent card (name, skills, extensions), MCP well-known manifest, llms.txt, robots.txt, and whether the root answers HTTP 402 with x402 payment requirements (and on which networks)
$0.010000GET https://agent-trust.agent-utils.workers.dev/v1/domainAgent-readiness and identity profile of a domain: Web Bot Auth key directory (RFC 9421), A2A agent card (name, skills, extensions), MCP well-known manifest, llms.txt, robots.txt, and whether the root answers HTTP 402 with x402 payment requirements (and on which networks). Use to decide whether a counterparty domain is a real agent service and how to talk to it.
Verifies a Web Bot Auth signed HTTP request (RFC 9421 HTTP Message Signatures) against the signer's public key directory: pass the request method, URL and the Signature, Signature-Input and Signature-Agent headers you received; get back whether the signature is valid, which agent directory signed it and the key id
$0.005000POST https://agent-trust.agent-utils.workers.dev/v1/verify-requestVerifies a Web Bot Auth signed HTTP request (RFC 9421 HTTP Message Signatures) against the signer's public key directory: pass the request method, URL and the Signature, Signature-Input and Signature-Agent headers you received; get back whether the signature is valid, which agent directory signed it and the key id. For sellers who cannot run the verification library themselves.
Checks
reachable
valid
2026-10-21T20:32:03.706Z
No settlement evidence found in chain signals.
Gateway routing
Score ≥70/100 — Cleared attestation pass. Route via Gateway before pay.
Claim this listing to upgrade to Cleared attestation.
Claim listing