API reference
GET /v1/status — health checks and monitoring
Check entitlement, plan and Claude connection state from your own monitoring with a single authenticated request. Response format and alerting tips.
Updated
/v1/status is the cheap call for dashboards, uptime checks and deploy gates: it verifies your key, reports the plan and tells you whether Claude is connected — without sending a prompt.
terminal
200 OK
What to alert on
provider.statusis anything butconnected— requests will return409 provider_not_connected.account.subscription_statusispast_due,unpaidorcanceled— renew on the billing page before access pauses.- HTTP
401— the key was revoked or rotated; update the environment.
All public endpoints
- POST
/v1/messagesSingle normalized message request. - POST
/v1/conversationMulti-turn normalized conversation request. - POST
/v1/conversation/streamSSE response stream using the same gateway. - GET
/v1/modelsAvailable public model aliases. - GET
/v1/statusAccount entitlement and Claude connection status.
Frequently asked questions
- Does /v1/status count towards rate limits?
- Yes, like every call — so poll it every minute or two, not every second.
- Is there an unauthenticated health endpoint?
- Not for customer data. Public endpoints always require a key; a failed key check answers 401 quickly, which is itself a useful signal.