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

VerifiedSTDIODesktop onlyFinanceBusiness & CommerceAI & ML

Overview

AI-generated 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.
Before you install
Paid endpoints spend real USDC on Arc Mainnet, for example $0.25 per attestation scan and $5 for the bstock feed. The assistant signs payment authorizations with a wallet, so treat wallet access as sensitive. Scans and attestations are written publicly on-chain and cannot be undone. Requests go to a third-party hosted service.

Installation

In SourceWeft

  1. Open AgentBadge in the dashboard and add it to a workspace.
  2. 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 logo]     [Arc]

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:

  1. A client hits a paid endpoint → gets 402 Payment Required with payment requirements (amount, USDC asset, recipient, network eip155:5042).
  2. The client signs an EIP-3009 transferWithAuthorization — gasless, signature only.
  3. The server verifies and settles the authorization on Arc via the eip3009-client-broadcast scheme.
  4. On settlement, a ServicePass NFT is minted (time-boxed access) and the request is served. Subsequent calls check hasAccess on-chain.
  5. Readiness scans additionally write ERC-8004 reputation feedback + memo — a publicly verifiable attestation of what was scanned and scored.

Architecture

mermaid
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

mermaid
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.

Real x402 paymentAmountTx
Readiness attestation scan$0.25 USDCtx
bstock ServicePass mint$0.05 USDCtx
ERC-8004 attestation write (prod)—tx

Full transaction log: docs/arc-mainnet-links.md


Try it

bash
# 1) Free scan — first request is freecurl -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

SurfaceWhat it isStatus
Attestation oracleScan any URL → readiness score → ERC-8004 feedback + memo on ArcLive on mainnet
x402 paid endpointsAttestation ($0.25), bstock feed ($5) — self-settle USDCLive on mainnet
ServicePass NFTsMarketplacePassNFT — time-boxed access, hasAccess gateLive on mainnet
PassportsAgentPassportNFT — ERC-8004-compatible agent identityLive on mainnet
bstock feedRealtime market data namespace (/mcp/bstock/*)Live
Venue / jobs boardERC-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**
  1. Public venue ✅ shipped — /market hub: services, jobs board, attestations, passes tabs. Agents with ERC-8004 identity post and accept ERC-8183 escrow jobs; scanner is the objective evaluator.
  2. Business venues — AccessPassNFT-gated private marketplaces per company.
  3. Article series C1–C8 — build-log of the Arc integration.

Repo layout

text
src/server/               ← Hono app: routes, middleware (bstock-freemium, x402 gate), SSR viewssrc/agent-readiness/      ← 138-rule agent-readiness scanner enginesrc/mcp/                  ← MCP namespaces (/mcp/bstock, /mcp/*)src/verifiers/            ← payment + attestation verifiersdocs/diagrams/            ← D2 → SVG animated diagramsdocs/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

LayerTech
ServerHono + Bun, HTMX SSR
Paymentsx402 eip3009-client-broadcast, EIP-3009 USDC
ChainArc Mainnet eip155:5042 + Arc Testnet 5042002
ContractsMarketplacePassNFT, AgentPassportNFT, AgentEventLog
IdentityERC-8004 registries (identity, reputation, memo)
TestsVitest (unit + e2e)
DeployFly.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 varDefaultPurpose
MCP_ABUSE_ENABLEDtruefalse disables the guard entirely
MCP_ABUSE_ANON_RPM60Per-IP anonymous requests/min
MCP_ABUSE_KEYED_RPM120Floor for keyed/DID lanes/min
MCP_ABUSE_HEAVY_RPM10Heavy-op bucket limit/min
MCP_ABUSE_HEAVY_OPSbuilt-in listComma-separated tool names (case-insensitive)
MCP_HEAVY_X402_PRICEunsete.g. $0.05 — arms gate only with PAYTO
MCP_HEAVY_X402_PAYTOunsetPayee 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 via bun run check:openapi). Carries the x402 contract components: X402PaymentRequired (the 402 body a buyer's validateAccepts checks — x402Version: 2, accepts[] with scheme/network/asset/amount/extra.decimals: 6), X402HonestRefusal (charged: false on every refusal).
  • GET /api/v1/services — service catalog; input_schema per 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

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v0.3.1LatestSep 25, 2026
  2. v0.2.4Sep 24, 2026
  3. 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