agentsvc.io primary sources — 2026-05-03

Project status in this pass

• No canonical standalone agentsvc.io whitepaper or litepaper surfaced.
• The clearest current sources of truth were the official site, official docs, machine-readable catalog and marketplace manifest, OpenAPI document, and the first-party MCP server repository.
• The materials consistently frame agentsvc.io as a service-discovery and micropayments layer for autonomous clients rather than as only a small bundle of utility APIs.

Primary-source snapshots

1) Official homepage

• URL: https://agentsvc.io/
• Key excerpt:
  • The homepage calls agentsvc.io “The Marketplace Where Agents Trade Services.”
  • It says agents can discover, call, and pay for services autonomously using x402 and USDC on Base.
  • It presents the product as a marketplace with 20 services, no-signup access, and a machine-readable API surface rather than as a conventional SaaS dashboard.

2) Official docs

• URL: https://agentsvc.io/docs
• Key excerpt:
  • The docs describe a simple workflow: list services, call a service without payment, receive HTTP 402 Payment Required, then sign and attach an X-Payment header.
  • The docs explicitly say payments run on x402 with USDC on Base and that no subscription is required.
  • The API reference also documents shared service schemas, query filters, and repeated endpoint patterns across the marketplace.

3) Machine-readable service catalog

• URL: https://agentsvc.io/api/v1/services
• Key excerpt:
  • The catalog returns structured per-service records with slug, name, description, category, endpoint, price in USDC, p99 latency, input schema, output schema, provider, and tags.
  • This is strong evidence that discovery is a first-class part of the product.
  • The presence of schemas and prices in the catalog suggests the marketplace is designed for software agents to choose and call tools programmatically.

4) Marketplace manifest

• URL: https://agentsvc.io/.well-known/agent-services.json
• Key excerpt:
  • The manifest describes agentsvc.io as an “Agent-to-agent service marketplace.”
  • It publishes the catalog endpoint, execution endpoint template, payment protocol, supported currency, chain, USDC contract, receiving wallet, docs URL, OpenAPI URL, and MCP server URL.
  • It also includes a step-by-step agent workflow and quickstart fields, which makes the project unusually explicit about agent-native integration.

5) OpenAPI document

• URL: https://agentsvc.io/api/openapi.json
• Key excerpt:
  • The OpenAPI file embeds agent workflow instructions directly in the info object, including discovery, 402 handling, payment signing, and manifest discovery.
  • It defines a dedicated x402Payment security scheme via the X-Payment header.
  • This reinforces that the platform is not just exposing endpoints, but standardizing how agents should discover and pay for them.

6) MCP server repository

• URL: https://github.com/jakobautomation/agentsvc-mcp
• Key excerpt:
  • The repository describes a single MCP server exposing 20 pay-per-call tools via x402 micropayments on Base.
  • It says the MCP server auto-discovers tools from the live catalog at startup.
  • This is important because it shows the marketplace, payment flow, and agent-runtime integration are designed to work as one system.

Working conclusion

agentsvc.io is best cataloged as an agent-service marketplace and x402 micropayments control plane. The decisive signals are the machine-readable catalog, the published manifest and OpenAPI file, the explicit 402 payment flow, and the MCP server that consumes the same live marketplace surface.