Services tagged “missing-data”
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.
| Our checks (unpaid requests) | Payment terms | Reported by the registry | Listing | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Service | Latest scheduled check | Last 30 checks, oldest to newest | Scheduled checks passed (7-day window) | Scheduled checks passed / run (30-day window) | Response time of latest check (ms) | Check schedule | Freshness | Monitoring since | Lowest price per call (US$) | Access | Payment protocols offered | Payment networks | Payment-terms changes (90 days) | Registry: unique payers (30 days) | Registry: paid calls (30 days) | What it does (capability tree) | Type | Added from | Purpose tags | Provider | Endpoint we check |
| Foundry PAR-007foundry-par007-machine-revenue-m… | Client error (4xx) · HTTP 415 | 0 passed, 2 failed, 28 not run, of the last 30 checks | short history0 of 2 run | short history0 of 2 run · 0 missed · 1 day | 72 | daily | Fresh | 2026-10-16 | $0.01registry's terms | — | — | eip155:8453 | — | 1 | 1 | Other (not placed in a branch yet) | Paid API | A public registry | csvdata-qualityschema-inference+2 | inference-chip-index.workers.dev6 endpoints | POST foundry-par007-machine-revenue-mainnet.i… |
22 columns; scroll sideways for more. Each heading links to its definition in the field dictionary. Registry columns are the registry's own figures.