Status feed API

The platform's last 24 hours: task success rate, median solve time and API availability. Public, with no key or session, and cacheable.

Every operation of the API reference is generated from the contract the API serves, version 0.1.0. Replace YOUR_API_KEY in the samples with your key.

Platform status

GET/v1/status

The last 24 hours of the platform, as the status page shows them: the share of finished tasks that succeeded, the median time to a token, and the share of minutes in which the API was serving. A figure drawn from too few tasks, or with no minute to judge yet, is null. It needs no key or session. Every caller gets the same reply, which caches may keep for a minute. Requests have a budget per client address.

Authentication: None: anyone may call it, within a budget per client address where the description says so.

Responses

Responses of Platform status
Status	Meaning	Body
200 OK	The figures.	StatusReport (application/json)
429 Too Many Requests	Over the budget of this client address (`rate_limited`); retry after `Retry-After`.	Problem (application/problem+json)
503 Service Unavailable	The figures cannot be read now (`service_unavailable`): the database cannot be reached, or this instance is shedding load. A status page shows the status as unknown.	Problem (application/problem+json)
Any other status	An error, as RFC 9457 problem details.	Problem (application/problem+json)

Error codes

rate_limited, service_unavailable. The errors reference says what each means, whether a retry helps and what it costs.

Sample

curl https://api.zerocaptcha.io/v1/status

const response = await fetch("https://api.zerocaptcha.io/v1/status");
console.log(response.status, await response.text());

import requests

response = requests.get(
    "https://api.zerocaptcha.io/v1/status",
    timeout=30,
)
print(response.status_code, response.text)