For agents & developers
Four ways in, one catalog. No API key during the pilot.
MCP
Remote MCP server over Streamable HTTP at https://agentsupply.dev/mcp. Supports protocol 2026-07-28 (stateless: server/discover, per-request _meta) and the initialize handshake of 2025-03-26 … 2025-11-25. Responses are plain JSON; no sessions.
{
"mcpServers": {
"agentsupply": {
"type": "http",
"url": "https://agentsupply.dev/mcp"
}
}
}
Tools: list_services, get_service, submit_request, get_request_status, check_eu_vat, lookup_lei, check_email_domain.
curl -s https://agentsupply.dev/mcp -H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-H 'MCP-Protocol-Version: 2026-07-28' -H 'Mcp-Method: tools/list' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{"_meta":{
"io.modelcontextprotocol/protocolVersion":"2026-07-28"}}}'
A2A
Agent card: /.well-known/agent-card.json (A2A v1.0). JSON-RPC endpoint: https://agentsupply.dev/a2a. Methods: SendMessage, GetTask (v0.3 names message/send, tasks/get are accepted). No streaming or push notifications yet.
curl -s https://agentsupply.dev/a2a -H 'content-type: application/json' -H 'A2A-Version: 1.0' -d '{
"jsonrpc":"2.0","id":1,"method":"SendMessage",
"params":{"message":{"messageId":"m1","role":"ROLE_USER",
"parts":[{"text":"We need 50 merchant legitimacy checks per week, max EUR 1 each."}]}}}'
Plain-text messages become service requests (task state TASK_STATE_SUBMITTED). Send a data part {"tool":"check_eu_vat","arguments":{…}} to run a live tool, or {"skill":"service-catalog"} to receive the catalog. Task states follow our review: quote → INPUT_REQUIRED, declined → REJECTED, fulfilled → COMPLETED.
Local MCP server (open source)
Prefer running checks locally? eu-kyb-mcp is our MIT-licensed stdio MCP server with the same VAT, LEI and email-domain checks.
claude mcp add eu-kyb -- npx -y github:mastermabel/eu-kyb-mcp
REST
OpenAPI 3.1: /openapi.json · API catalog (RFC 9727): /.well-known/api-catalog
# catalog
curl -s https://agentsupply.dev/api/v1/services
# request a service
curl -s -X POST https://agentsupply.dev/api/v1/requests -H 'content-type: application/json' -d '{
"service_id": "business-phone-check",
"problem": "Confirm opening hours and wheelchair access for 20 clinics in Berlin.",
"frequency": "one_off", "max_price_per_unit": 8, "currency": "EUR",
"urgency": "this_week", "requester_type": "autonomous_agent",
"agent_name": "care-finder", "contact_email": "ops@example.com"}'
# poll status (token from the receipt)
curl -s "https://agentsupply.dev/api/v1/requests/req_…?token=tok_…"
# live tool
curl -s -X POST https://agentsupply.dev/api/v1/tools/check-eu-vat -H 'content-type: application/json' \
-d '{"vat_number":"DE123456789"}'
Request fields
Only problem is required. Everything else helps us prioritise: service_id, frequency, monthly_volume, max_price_per_unit, monthly_budget, one_off_budget, currency, pricing_model, payment_methods, urgency, interface_pref, max_latency, requester_type, agent_name, agent_platform, operator, agent_card_url, contact_email. Full schema: OpenAPI → ServiceRequest.
Markdown for agents
Send Accept: text/markdown to /, /services or /services/{id} to receive Markdown instead of HTML. llms.txt and llms-full.txt summarise everything.
Limits & fair use
- Live tools: 100 calls per client per day during the pilot.
- Requests: 10 per client per hour.
- Need more? Submit a request with your expected volume.
Payments roadmap
Nothing is charged during the pilot. Once demand is confirmed we plan, in this order: invoices / payment links for quoted work → prepaid credits with API keys → per-call machine payments (e.g. HTTP 402 / x402 with stablecoins) for automated services. Tell us which you need via payment_methods.