Check that the API can serve requests
GET
/readyzA readiness check for load balancers and uptime monitors. It answers 200 with an empty body when the API can reach the two shared services it needs to count credits and to cache answers, and 503 when it cannot. Use it to decide whether to send traffic to the API. It does not check the chains themselves; /v1/status shows how far each chain has progressed.
There is nothing to send.
Response
The API can serve requests. The body is empty and the answer is never cached.
Cost
Free. It uses no credits and does not count toward your per-IP rate limit. Only the looser ceiling shared by every caller on your network applies, and above it you get 429 rate_limited.
Errors
503 with an empty body when either shared service does not answer.