agentsvc.io

• Name: agentsvc.io
• URL: https://agentsvc.io/
• Category: x402 service marketplace / seller wrapper
• Tags: ethereum-ecosystem
• Summary: agentsvc.io is a small x402 service shelf. Most of the tools are generic. Keep the note for the packaging: one operator publishes the catalog, schemas, marketplace manifest, OpenAPI surface, and MCP server around the same USDC-on-Base flow.
• What it does:
  • Publishes a marketplace of pay-per-call services for agents, spanning screenshots, webpage reading, weather, exchange rates, DNS, QR generation, news search, crypto prices, OCR, PDF extraction, geocoding, and other utility/data endpoints
  • Exposes a machine-readable catalog at /api/v1/services with per-service price, latency, input schema, output schema, endpoint URL, tags, and active status so software agents can discover services without scraping HTML
  • Uses the x402 protocol with USDC on Base so callers can probe a service, receive an HTTP 402 Payment Required response, sign the payment, and retry with an X-Payment header
  • Publishes both an OpenAPI 3.1 spec and a .well-known/agent-services.json manifest that repeat discovery, pricing, and payment semantics for autonomous clients
  • Ships a first-party MCP server that auto-discovers the live catalog and exposes the paid tools directly inside MCP-compatible agent environments
• Key claims:
  • The homepage explicitly calls agentsvc.io “The Marketplace Where Agents Trade Services,” which is the clearest signal that the project wants to be a small service market rather than a single API product
  • The official docs say there is no signup or API key requirement and that agents can probe an endpoint, receive a 402, and retry with an X-Payment header, which cleanly reinforces the open paid-request model
  • The machine-readable marketplace manifest says the platform is an agent-to-agent service marketplace with a catalog endpoint, execution template, x402 payment protocol, USDC support on Base, and a published receiving wallet
  • The OpenAPI document embeds agent workflow instructions directly in the schema, including discovery, 402 handling, payment signing, manifest discovery, and MCP access
  • The MCP server repo says the platform exposes around 20 pay-per-call tools via x402 and auto-discovers them from the live catalog, showing the marketplace and MCP layer are coupled parts of one small operating model
  • The per-service catalog publishes micropayment pricing, schemas, and latency numbers, which is enough to make the product machine-usable instead of just browseable marketing copy
• Whitepaper: No canonical standalone agentsvc.io whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, docs, machine-readable catalog and marketplace manifest, OpenAPI document, and first-party MCP server materials; see ../whitepapers/agentsvc-io-primary-sources-2026-05-03.md.
• Sources:
  • https://agentsvc.io/
  • https://agentsvc.io/docs
  • https://agentsvc.io/api/v1/services
  • https://agentsvc.io/.well-known/agent-services.json
  • https://agentsvc.io/api/openapi.json
  • https://github.com/jakobautomation/agentsvc-mcp

Internal linkages

• Protocol base: x402
• Stronger directory reference: 402-index

Control surface

• The operator controls catalog admission, schema shape, endpoint metadata, MCP packaging, and which paid utilities get first-class discovery.

• That is enough to matter, but it is still wrapper power, not rail power.

• Read agentsvc.io as a small seller-and-directory layer riding on stronger payment standards.

• Last reviewed: 2026-06-03 UTC