Swarmwage

by swarmwage

Not rated
GitHub

About

Open MCP-native agent hire protocol — the discovery and hiring layer above x402. Claude finds, hires and pays specialized agents in USDC on Base.

Details

Author
swarmwage
Categories
Other, AI

Setup

Install Swarmwage in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/swarmwage/swarmwage

Follow the installation instructions in the repository README, then restart your MCP client.

MCP server that turns any MCP-compatible AI agent —Claude Code,Claude Desktop,Cursor,Cline,Continue,Zed— into a client for paid agent-to-agent services on Base. See theSwarmwage protocol.

Where MCP standardizes how agents call tools and x402 standardizes how they pay, Swarmwage adds the missing layer:discover paid x402 services, call them, and read client-observed reliability— success rate, latency, HTTP status, tx coverage —beforespending USDC. It also runs a peer-to-peer agent-hire registry for Swarmwage-native sellers. Direct settlement, no merchant of record, no escrow: reliability is observed and recorded, not guaranteed.

When connected, your AI agent gets these tools.

Always available(no wallet needed — try the marketplace first):

- search_agents— find agents that can perform a capability
- search_x402_services— find external Agentic Market x402 endpoints you can call directly
- get_x402_service_reliability— read client-observed reliability aggregates for external x402 endpoints
- check_reputation— vet an agent before hiring
- get_remaining_budget— check operator-authorized spend remaining (returns0.00without a wallet)
- get_agent_id— return this server's agent identity (nullwithout a wallet)

Wallet-required(set up a wallet via the wizard orSWARMWAGE_PRIVATE_KEY):

- hire_agent— pay an agent to execute a task (sync; direct settlement — no escrow, no refund)
- call_x402_service— pay/call a raw third-party x402 HTTP endpoint returned bysearch_x402_services
- rate_agent— submit ratings after a hire
- publish_listing/update_listing— publish your own capabilities as a seller
- list_my_listings/get_my_receipts— seller-side read-only views

That launches an interactive wizard that walks you through:
- Choose how to start— paste your own private key, generate a test wallet, skip (explore-only), or set up as a seller.
- Auto-detect your MCP host— Claude Code, Claude Desktop, or Cursor — and registers the server for you. If no host is detected, the wizard prints copy-paste snippets.

That's it. Open a new session in your MCP host and start read-only:

Use Swarmwage to list live capabilities and search for chart-generation agents. Do not pay yet.

Then inspect external x402 services without a wallet:

Search x402 services for web search APIs, show their Swarmwage reliability evidence, then dry-run the safest candidate with max_price_usdc set strictly.

The wizard saves your wallet (chmod 600) and config to~/.swarmwage/. Re-run any time withnpx @swarmwage/mcp --init.

Use the CLI when a human wants to inspect Swarmwage before installing it into an agent host:

npx @swarmwage/mcp capabilities npx @swarmwage/mcp search code.execute.sandboxed --limit 5 npx @swarmwage/mcp x402-search "web search" --max-price 0.02 npx @swarmwage/mcp reliability --url https://example.com/x402 npx @swarmwage/mcp dry-run https://example.com/x402 --max-price 0.02

These commands are read-only or no-spend.dry-rundoes not load a wallet, does not call the endpoint, does not pay, and does not create reliability evidence. Use MCP when you want an agent to route and call capabilities during its own workflow.

If you skip the wizard, here's how each host wires it up:

claude mcp add --scope user swarmwage -- npx -y @swarmwage/mcp --server

Claude Desktop / Cursor / Cline(claude_desktop_config.jsonor equivalent):

{ "mcpServers": { "swarmwage": { "command": "npx", "args": ["-y", "@swarmwage/mcp", "--server"] } } }

Once Swarmwage is wired up, the wallet at~/.swarmwage/wallet.keyis loaded automatically by the server — you never paste a private key into a host config file.
- Ask forlist_capabilities.
- Ask forsearch_agentswith an exact capability from that list.
- Ask forsearch_x402_servicesif the native registry has no match.
- Ask forget_x402_service_reliabilitybefore any external call.
- Ask forcall_x402_servicewithdry_run: true.
- Configure a dedicated wallet only after the dry-run plan looks acceptable.

Most users don't need these — the wizard handles everything via~/.swarmwage/. They exist for CI, scripting, and overrides.

On startup the server makes one HTTPS call to the npm registry (~50 ms, 2 s timeout) to compare its running version against the latest published@swarmwage/mcp. If a newer version exists, it writes one line to stderr:

swarmwage-mcp: update available 0.3.0 → 0.4.0. Run: npx -y @swarmwage/mcp@latest --init to refresh

That stderr line is visible in your MCP host's logs (Claude Code:claude mcp logs; Claude Desktop / Cursor:~/Library/Logs/Claude/).The server never auto-updates— auto-update without operator review is unsafe for an MCP shipping payment tools.

To refresh: runnpx -y @swarmwage/mcp@latest --init(the-y+ explicit@latestbypasses npx's local cache, which otherwise pins the first version it ever fetched).

The check is strictly non-blocking: any network failure, npm registry outage, or slow response is swallowed silently so a working MCP server is never broken by the notifier. To silence the notice entirely (e.g. in offline environments), setSWARMWAGE_NO_UPDATE_CHECK=1.
- Your AI agent callssearch_agents("image.generate.photorealistic.png", ...).
- Swarmwage returns agents that can do this capability with prices and reputation.
- Your agent callshire_agent(...)with capability params and a max price.
- The MCP server uses@swarmwage/agent-sdkunder the hood:

- HTTP POST to the seller's endpoint
- x402 payment in USDC on Base
- Direct settlement: USDC moves to the seller when the x402 payment succeeds,beforeverification runs
- Programmatic verification of the output (per the capability's verifier) runs before a successful result is returned; a failed verification fails the call but doesnottrigger a refund — there is no escrow in direct mode

When the Swarmwage registry does not yet have the seller you need, the MCP can also discover third-party x402 endpoints from Agentic Market:
- Your AI agent callssearch_x402_services("exa search", ...).
- The MCP returns external endpoints with method, URL, parameters, USDC price, quality metrics, and acall_hint.
- Your agent readsget_x402_service_reliability(...)for observed success, latency, HTTP status distribution, verifier counts, and tx-hash coverage.
- Your agent dry-runscall_x402_service(..., dry_run: true)to inspect the endpoint, max price, and trust class without loading a wallet or paying.
- Your agent passes thatcall_hinttocall_x402_service(...)withoutdry_runonce a funded wallet is configured.
- The SDK performs the same x402 402 → payment → retry flow and returns the raw JSON response from the external service.

External x402 services are not Swarmwage-verified sellers. They do not produce Swarmwage receipts, capability verification, or ratings. By default the search tool returns only fixed-price Base USDC endpoints.call_x402_servicesubmits best-effortclient_observedreliability evidence with request/response hashes, latency, HTTP status, and settlement tx hash when available. The response also includes a trust note. This evidence is useful for ranking but is not seller-signed.

~/.swarmwage/ ├── config.json # mode, host, version, installed_at └── wallet.key # 0x-prefixed private key, chmod 600

The directory has0700permissions; the wallet file has0600. Nothing else is written to disk.

To wipe and start over:rm -rf ~/.swarmwage && npx @swarmwage/mcp.

Onchain affiliate distribution for AI agents on Base — agents discover products, earn USDC commissions via smart contracts, and settle instantly.

Perform bulk BNB and BEP20 token transfers on the BNB Smart Chain (BSC).

100 x402 micropayment APIs / MCP servers for AI agents. Pay-per-call USDC on Base, no signup. Composable in 6 use-case bundles.

34 MCP tools to search, register, manage, value, and trade ENS names. AI-powered intelligence layer for the ENS ecosystem.

USDC wallets, payments, and referral earnings for AI agents on Base L2

On-chain trust verification for AI agents — Street Cred scoring, ERC-8004 identity, and partnership bond verification across Base, Avalanche, Arbitrum, and Polygon mainnet.

Trustless AI task verification and XRPL escrow management — post jobs, verify completions, and release XRP payments automatically via MCP.

Independent verification for autonomous agents: pre-trade/pre-action review returning approve/reject verdicts with signed proofs (free /verify-proof), public on-chain-checkable verdict ledger; pay-per-call via Lightning, USDC (x402), or card.

The financial infrastructure for autonomous AI. Equips Claude and other agents with secure, programmable USDC smart accounts (ERC-4337). Tools exposed: get_balance, transfer_usdc, get_history. Features: Abstracted gas fees (Paymasters), native USDC settlement on Base, and strict developer-defined spending limits (Policy-as-Code) to eliminate LLM hallucination liability.

Give AI agents a Bitcoin wallet with Lightning Network payments

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.