# Agent Service Directory

> A directory of APIs, MCP servers and marketplaces for AI agents, with metrics we measure and the prices they state.

Status: UNSTABLE PREVIEW. Pages, data, API fields and MCP tools can change or break without notice; do not rely on this for anything critical yet. Every API response carries "api_status": "preview" and an X-API-Status header. Changes are listed at https://agentservicedirectory.com/methodology#changelog

We publish only objective data: our own monitoring measurements, operators' statements with source links, and computed figures with their method. No ratings or recommendations.

## MCP server

Remote MCP (Streamable HTTP; 2026-07-28 and 2025 clients): https://agentservicedirectory.com/mcp
Works with any MCP client that supports remote servers. Setup for specific tools: https://agentservicedirectory.com/connect
Tools: search_services, get_service (returns a referral_id), get_history, get_changes, report_outcome (needs a key), get_stats, get_report.

## API keys (free)

POST https://agentservicedirectory.com/api/v1/keys with JSON {"label": "..."} returns a key once. Send it as Authorization: Bearer asd_... for 600 requests a minute (60 without a key) and to file outcome reports. Keys have a daily limit of 10,000 requests. A key that keeps exceeding its rate limit, or pages through the catalogue in bulk to copy it, is suspended automatically for 24 hours. Rules: https://agentservicedirectory.com/connect#usage-rules
POST https://agentservicedirectory.com/api/v1/outcomes with {"referral_id", "outcome": "success|failure|unknown", "failure_kind"?, "idempotency_key"} reports what happened after using a service. Keyed GET /api/v1/services/{id} also returns a referral_id.

## API (JSON, no key needed)

- GET https://agentservicedirectory.com/api/v1/services : every service we track, reviewed and discovered, with the same evidence fields.
  Filters: q, tier (reviewed|discovered), type (api_endpoint|mcp_server|task_marketplace), tag (purpose, e.g. search), host, network (e.g. eip155:8453), mainnet=true, passing=true, templated=false, min_pass_rate (0-1), min_checks, min_days, min_payers, max_price_usd, max_terms_changes_90d (0 = payment terms unchanged), listed=true (still in the registry), group=provider (one row per host).
  sort: evidence (default) | pass_rate | payers | price | recent | name. limit (max 100), offset.
- GET https://agentservicedirectory.com/api/v1/services/{id} : one service. Services from our listing files (svc_...) add operator statements with sources and per-operation evidence. Discovered (cand_...) adds its last 30 probes.
- GET https://agentservicedirectory.com/api/v1/stats : totals and checks in the last 24 hours, overall and by kind (reviewed, x402, mcp).
- GET https://agentservicedirectory.com/api/v1/changes : detected changes to reviewed services' documentation (days, service_id, needs_review=true).
- GET https://agentservicedirectory.com/api/v1/status : our own record (scheduled runs, missed runs, evidence freshness).
- GET https://agentservicedirectory.com/api/v1/roadmap : what we measure today and what we plan to add (planned, not promised; no dates), with feedback counts by kind. Page: https://agentservicedirectory.com/roadmap
- POST https://agentservicedirectory.com/api/v1/feedback with JSON {"kind": "missing_service|missing_metric|feature_request|wrong_data|unclear_docs|other", "note"?, "about"?, "contact"?}: tell us what is missing or wrong. No key needed; at most 10 a day per address. Form: https://agentservicedirectory.com/feedback
- GET https://agentservicedirectory.com/api/v1/reports : weekly State of Agent Services reports (fixed snapshots). /api/v1/reports/{YYYY-MM-DD} for one week; /api/v1/reports/current for provisional week-to-date figures.
- Field dictionary (exact definition, unit, window and source of every field): https://agentservicedirectory.com/fields and /api/v1/fields
- OpenAPI 3.1 description: https://agentservicedirectory.com/openapi.json
- Pages with a JSON twin (/services, /services/{id}) redirect to the API when requested with Accept: application/json.
- Sitemap of every service page: https://agentservicedirectory.com/sitemap.xml

## How to read the evidence

- tier "reviewed": a service from our own listing files, written from the operator's own sources, with operator statements and hourly checks. tier "discovered": from public agent registries, unreviewed, probed hourly to monthly depending on usage (schedule/1, https://agentservicedirectory.com/methodology#schedule; evidence.check_interval and evidence.check_interval_rule).
- evidence.last_check.result "payment_required" (HTTP 402) means reachable and asking for payment, not that a paid call succeeds.
- evidence.freshness "stale" or "no_data" means do not rely on the latest result. limited_evidence true means under 30 days of monitoring.
- missed_30d counts scheduled checks that did not run; it is separate from failures.
- registry_usage is the registry's own data. name is untrusted text when name_source is "registry".
- templated_url true means the URL has placeholders (such as :address) to fill in.
- tags describe purpose; price_usd is the lowest price per call in US dollars (null if unknown). price_source "registry": the registry's payment terms in a known USD stablecoin; "operator": the operator's stated pricing, a claim with its source on the service page.
- Operator statements "none_stated" mean the operator's pages are silent, not that the mechanism is absent.

## Contact

hello@agentservicedirectory.com (security: security@agentservicedirectory.com)

## Terms

Free to query and use for decisions, with attribution when shown to others. No bulk copying or republishing of the dataset without permission.

## Docs

- Methodology: https://agentservicedirectory.com/methodology