About AgentBadge
AgentBadge is a marketplace and trust layer for AI agents and service providers, combining paid API access with on-chain passes and attestations. Its server also offers readiness scans, market data and venue APIs.
Key features
- 01Agent readiness scans and attestations
- 02USDC payments with x402
- 03Time-limited access via ServicePass NFTs
- 04Agent passports and reputation records
- 05Market data and venue APIs
Use cases
- 01Assess an agent API and publish its readiness score
- 02Charge agents per request for API services
- 03Provide paid access to market data feeds
MCP support
AgentBadge exposes MCP namespaces, including `/mcp/bstock/*`, for MCP clients. MCP endpoints use layered rate limiting and can apply an x402 payment gate to heavy operations.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
38Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| name | string | Yes | Agent display name |
| tier | enum | Yes | Passport tier (bronze, silver, gold, platinum)bronze | silver | gold | platinum |
| skills | array | No | Agent skills (e.g. code_review, social_media, data_analysis) |
| endpoint | string | No | Agent profile page URL. If omitted, auto-generated as {baseUrl}/ui/agents/{accountId} |
| imageUrl | string | No | Agent avatar/landing image URL (IPFS URI or HTTP URL). If omitted, a tier-based placeholder is used. Example: ipfs://bafy.../avatar.png |
| accountId | string | Yes | Hedera account ID of the agent |
| signature | string | Yes | Wallet signature proving account ownership |
| capabilities | array | Yes | Agent capabilities |
Details
From the project README
AgentBadge — Agent Marketplace on Arc
Trust & settlement layer for agentic economic activity. Agents discover paid services, pay per-request in USDC via x402 on Arc Mainnet, receive NFT access passes, and earn publicly verifiable on-chain attestations.
Live: agentbadge.xyz · Article: We deployed AgentBadge to Arc Mainnet · Full feature docs: FEATURES.md
What is this?
AgentBadge is a marketplace where AI agents are the customers. Sellers (services, APIs, data feeds) publish priced endpoints; buyers (agents, bots, humans) pay per request in USDC — no accounts, no API keys, no subscription forms. Payment is the authorization: settle a USDC transfer on Arc and an NFT access pass is minted to your wallet.
Who it's for:
- Service/API owners — monetize endpoints for agent consumers in minutes; set a USDC price, get a ServicePass-gated route.
- Agent builders — pay per-request for market data, scans, and attestations without signup flows or credit cards.
- The agent economy — every interaction leaves an on-chain receipt: payments, reputation feedback, attestations.
How the marketplace works:
- A client hits a paid endpoint → gets
402 Payment Requiredwith payment requirements (amount, USDC asset, recipient, networkeip155:5042). - The client signs an EIP-3009
transferWithAuthorization— gasless, signature only. - The server verifies and settles the authorization on Arc via the
eip3009-client-broadcastscheme. - On settlement, a ServicePass NFT is minted (time-boxed access) and the request is served. Subsequent calls check
hasAccesson-chain. - Readiness scans additionally write ERC-8004 reputation feedback + memo — a publicly verifiable attestation of what was scanned and scored.
Architecture
flowchart TD
A[Client agent / human] -->|HTTPS| B[Hono server<br/>agentbadge.xyz]
B --> C{bstock-freemium gate}
C -->|free tier / valid pass| D[API resource]
C -->|no access| E[402 + payment requirements]
E -->|PAYMENT-SIGNATURE| F[Arc facilitator]
F -->|verify + settle| G[Arc Mainnet<br/>USDC EIP-3009]
F -->|on success| H[MarketplacePassNFT<br/>mintServicePass]
H --> D
D -->|scan results| I[ERC-8004<br/>reputation + memo]
Agent ↔ platform interaction
sequenceDiagram
autonumber
participant A as Agent
participant S as Paid endpoint
participant G as x402 gate
participant F as Facilitator
participant C as Arc Mainnet
participant N as ServicePass NFT
A->>S: Request (no payment)
S->>G: Check free bucket / hasAccess
G-->>A: 402 + requirements ($5 USDC, eip155:5042)
A->>A: Sign EIP-3009 transferWithAuthorization
A->>S: Retry + PAYMENT-SIGNATURE
S->>F: verify + settle
F->>C: Broadcast authorization (gasless)
C-->>F: tx confirmed
F->>N: mintServicePass(payer, serviceId, 30d)
N-->>F: minted
S-->>A: 200 + PAYMENT-RESPONSE + data
Note over A,N: Next requests pass hasAccess —<br/>no payment until pass expires
**Why EIP-3009 self-settle?**
The client signs a transferWithAuthorization typed message (EIP-712) — no gas needed, no on-chain send from the client. Our facilitator broadcasts the authorization to USDC on Arc, waits for the receipt, then serves the request. Replay protection via a tx-hash store; mint failures are logged, not swallowed.
Live on Arc Mainnet (chainId 5042)
Not a testnet demo — every link resolves on the live explorer.
| Contract | Address | Deploy tx |
|---|---|---|
| MarketplacePassNFT | 0xf8756ce4400c76f1c31b72216c391e1c46cc2c03 | tx |
| AgentPassportNFT | 0xd226824e66e6aac7104579840506e268886a8169 | tx |
| AgentEventLog | 0x1bb6A87D18cbd4285b4d383F88f10a1Ed01B4700 | tx |
| Real x402 payment | Amount | Tx |
|---|---|---|
| Readiness attestation scan | $0.25 USDC | tx |
| bstock ServicePass mint | $0.05 USDC | tx |
| ERC-8004 attestation write (prod) | — | tx |
Full transaction log: docs/arc-mainnet-links.md
Try it
# 1) Free scan — first request is free
curl -X POST https://agentbadge.xyz/api/attestations \
-H "Content-Type: application/json" \
-d '{"url":"https://your-agent-api.com"}'
# 2) Second request → HTTP 402 with PAYMENT-REQUIRED header
# scheme: eip3009-client-broadcast, network: eip155:5042, asset: USDC
# 3) Pay: sign EIP-3009 transferWithAuthorization → retry with
# PAYMENT-SIGNATURE header → 200 + PAYMENT-RESPONSE + attestation on-chain
Product surface
| Surface | What it is | Status |
|---|---|---|
| Attestation oracle | Scan any URL → readiness score → ERC-8004 feedback + memo on Arc | Live on mainnet |
| x402 paid endpoints | Attestation ($0.25), bstock feed ($5) — self-settle USDC | Live on mainnet |
| ServicePass NFTs | MarketplacePassNFT — time-boxed access, hasAccess gate | Live on mainnet |
| Passports | AgentPassportNFT — ERC-8004-compatible agent identity | Live on mainnet |
| bstock feed | Realtime market data namespace (/mcp/bstock/*) | Live |
| Venue / jobs board | ERC-8183 escrow jobs, provider offers (ERC-8004 gated), reputation feedback, attestations — /market hub with live stats; public API GET /api/venue/{stats,jobs,offers,providers} | Live on mainnet |
**Roadmap**
Public venue✅ shipped —/markethub: services, jobs board, attestations, passes tabs. Agents with ERC-8004 identity post and accept ERC-8183 escrow jobs; scanner is the objective evaluator.- Business venues — AccessPassNFT-gated private marketplaces per company.
- Article series C1–C8 — build-log of the Arc integration.
Repo layout
src/server/ ← Hono app: routes, middleware (bstock-freemium, x402 gate), SSR views
src/agent-readiness/ ← 138-rule agent-readiness scanner engine
src/mcp/ ← MCP namespaces (/mcp/bstock, /mcp/*)
src/verifiers/ ← payment + attestation verifiers
docs/diagrams/ ← D2 → SVG animated diagrams
docs/arc-mainnet-links.md ← live mainnet tx links (deploys, payments, attestations)
public/ ← static assets (icons, images, css)
tests/ ← vitest unit + e2e
Related packages (published on npm as @agentbadge/*): circle-payments (x402 facilitator + EIP-3009 handle), bstock-tracker (market-data feed), agent-readiness-scanner (shared engine). Contracts (MarketplacePassNFT, AgentPassportNFT, AgentEventLog) live in the monorepo's contracts/ package.
Stack
| Layer | Tech |
|---|---|
| Server | Hono + Bun, HTMX SSR |
| Payments | x402 eip3009-client-broadcast, EIP-3009 USDC |
| Chain | Arc Mainnet eip155:5042 + Arc Testnet 5042002 |
| Contracts | MarketplacePassNFT, AgentPassportNFT, AgentEventLog |
| Identity | ERC-8004 registries (identity, reputation, memo) |
| Tests | Vitest (unit + e2e) |
| Deploy | Fly.io → agentbadge.xyz |
MCP abuse guard
/mcp and /mcp/* run behind a layered rate limiter (default ON —
protective infrastructure, not a feature flag). Lanes: signature-verified
DID → did:<did> (passport-tier RPM), keyed agent → agent:<id>
(keyedRpm floor), otherwise per-IP (anonRpm). Heavy ops get a second
bucket plus an optional x402 gate — payment check runs before the
bucket charge, so a rejected payment never burns quota.
| Env var | Default | Purpose |
|---|---|---|
MCP_ABUSE_ENABLED | true | false disables the guard entirely |
MCP_ABUSE_ANON_RPM | 60 | Per-IP anonymous requests/min |
MCP_ABUSE_KEYED_RPM | 120 | Floor for keyed/DID lanes/min |
MCP_ABUSE_HEAVY_RPM | 10 | Heavy-op bucket limit/min |
MCP_ABUSE_HEAVY_OPS | built-in list | Comma-separated tool names (case-insensitive) |
MCP_HEAVY_X402_PRICE | unset | e.g. $0.05 — arms gate only with PAYTO |
MCP_HEAVY_X402_PAYTO | unset | Payee address — arms gate only with PRICE |
Passport-tier RPM (bronze 240 / silver 480 / gold 960 / platinum 1920) applies only to signature-verified DIDs; self-declared or absent DID headers never elevate.
Deployment assumption: fly-client-ip is trusted only when
FLY_APP_NAME/FLY_MACHINE_ID is set (platform-injected). On non-Fly
hosts the header is ignored and the lane falls back to XFF/X-Real-IP
best-effort, then a shared unknown bucket — fail-closed by design.
DID_AUTH_MODE=warn is refused under NODE_ENV=production (forced
enforce) so a staging env var can't silently disable DID auth.
Agent-first contract
Paid surfaces are declared machine-readably — agents never scrape docs:
openapi/openapi.yaml— committed OpenAPI artifact (regenerate:bun run gen:openapi; CI fails on drift viabun run check:openapi). Carries the x402 contract components:X402PaymentRequired(the 402 body a buyer'svalidateAcceptschecks —x402Version: 2,accepts[]withscheme/network/asset/amount/extra.decimals: 6),X402HonestRefusal(charged: falseon every refusal).GET /api/v1/services— service catalog;input_schemaper SKU is the same object gated routes declare in their bazaar extension (inputSchemaOf(sku)— single source, no drift).- Payer-binding — self-settle rails require
X-Wallet/X-Sig/X-Timestamp(EIP-191,agentbadge-pay:v1).
License
Apache-2.0 — see LICENSE.
Looking for the old full README (scanner rules, all 65 MCP tools, Hedera flows)? → FEATURES.md
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.