Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory

Endpoints from regionfetch.dev

Every service we watch, including those that do not meet our listing criteria. The same metrics for each. Agents can run the same query at /api/v1/services.

More filters
Clear filters

2 matching · showing 1–2 · sorted by most evidence · page 1 of 1

Full tableChecksPayment termsRegistry figuresListing JSON

Our checks (unpaid requests)Payment termsOur checks (unpaid requests)Payment termsReported by the registryListing
ServiceLatest scheduled checkLast 30 checks, oldest to newestScheduled checks passed (7-day window)Scheduled checks passed / run (30-day window)Response time of latest check (ms)Check scheduleFreshnessMonitoring sinceLowest price per call (US$)AccessToolsPayment protocols offeredPayment networksPayment-terms changes (90 days)Registry: unique payers (30 days)Registry: paid calls (30 days)What it does (capability tree)TypeAdded fromPurpose tagsProviderEndpoint we check
Region Fetchregistry.npmjs.org Package available · HTTP 2001 passed, 0 failed, 29 not run, of the last 30 checksshort history1 of 1 runshort history1 of 1 run · 0 missed · under 1 day140weeklyFresh2026-10-18————————Fetch past blocksLocal MCP serverA public registry—regionfetch.dev2 endpointsGET www.npmjs.com/package/regionfetch-mcp
Region Fetchregionfetch.dev Client error (4xx) · HTTP 4000 passed, 2 failed, 28 not run, of the last 30 checksshort history0 of 2 runshort history0 of 2 run · 0 missed · 1 day258dailyFresh2026-10-18$0.02registry's terms———eip155:8453—11Other (not placed in a branch yet)Paid APIA public registryweb-fetchgeo-targetingbrowser+2regionfetch.dev2 endpointsPOST regionfetch.dev/api/fetch

23 columns; scroll sideways for more. Each heading links to its definition in the field dictionary. Registry columns are the registry's own figures.