
AgentBadge
io.github.spreadzpPublished by GitHub account spreadzpv0.3.1Updated Nov 3, 2026
AgentBadge MCP — agent-readiness scan, passport, discovery, marketplace and circle-payments tools
Overview
AgentBadge exposes an agent marketplace on Arc: readiness scans, passports, discovery, and USDC pay-per-request endpoints for an assistant.
- What you can do
- Scan a URL for agent readiness and write an on-chain attestation
- Look up marketplace services, jobs, offers and providers
- Handle passports and time-boxed ServicePass access passes
- Read the bstock market-data feed
- Pay per request in USDC over x402 when a free tier or pass is exhausted
- When to use it
- Worth adding when an assistant needs to check how agent-ready a service is, browse a marketplace of paid agent services, or pay per request in USDC on Arc instead of using accounts and API keys.
- Requirements
- Runs as a local npm package over stdio. It talks to the hosted agentbadge.xyz service over the network. Paid calls need a wallet that can sign EIP-3009 USDC authorizations on Arc Mainnet, plus X-Wallet, X-Sig and X-Timestamp headers for payer binding. No API keys or environment variables are declared.
Installation
In SourceWeft
- Open AgentBadge in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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
Agent ↔ platform interaction
**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.
Full transaction log: docs/arc-mainnet-links.md
Try it
Product surface
**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
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
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.
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
Source: README.md at commit cfccc73
Tools
0Version history
3- v0.3.1LatestSep 25, 2026
- v0.2.4Sep 24, 2026
- v0.2.3Sep 24, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts