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 bitbybit.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 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$)Payment 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
Bitbybit CAD Cloud MCPapi.bitbybit.dev Live, MCP endpoint answered · HTTP 4012 passed, 0 failed, 28 not run, of the last 30 checksshort history2 of 2 runshort history2 of 2 run · 0 missed · 1 day663dailyFresh2026-10-17——————3D models and design filesMCP serverA public registry—bitbybit.dev2 endpointsGET api.bitbybit.dev/mcp
Bitbybit CAD MCPmcp.bitbybit.dev Live, MCP endpoint answered · HTTP 4052 passed, 0 failed, 28 not run, of the last 30 checksshort history2 of 2 runshort history2 of 2 run · 0 missed · 1 day182dailyFresh2026-10-17——————3D models and design filesMCP serverA public registry—bitbybit.dev2 endpointsGET mcp.bitbybit.dev/mcp

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