Checking the public gateway endpoints. Each check has a 4-second timeout.
Service status
Public gateway checks and published notices for SaveMyToken Coding Plans. Check the scope and timestamp before using a result to diagnose your request.
Checks run when this page is requested and may be shared for 30 seconds. Each check uses a public health endpoint with a 4-second timeout. This page does not refresh automatically. Results older than 60 seconds when a snapshot is loaded are labeled stale; the original timestamp remains visible.
These are health-endpoint observations. Per-model inference, streaming, tool calls, image handling, payment processing and key delivery are not measured here. No uptime percentage, response-time benchmark or contractual SLA is established by these checks.
Published service notices
No operator notices have been published on this page yet. There is no connected historical incident feed; this empty list does not establish that services are incident-free. If you are experiencing a problem, use the steps below.
Your request is failing. What next?
401 or 403
Check that your key is active, the endpoint matches your plan family, and the requested model is permitted. Keep your key private. Open Billing & API keys.
429 or allowance errors
Check remaining allowance, reset times and request concurrency. A health-endpoint response does not test your account’s limits. Avoid repeated immediate retries.
5xx or timeouts
Keep the request ID, UTC time, model ID and error code. Check the notices above and your agent’s retry behavior. Confirm task state before resending an agent action; a lost response does not prove no action occurred.
Text works; tools or images fail
Use your agent’s setup and first-connection checklist. Verify the feature on your chosen model and client; the health check does not exercise these features.
Payment or missing key
Check your order in Billing & API keys. For delivery or billing support, include the order number and time; the gateway check does not verify payment or delivery.
Contact setup and usage support with your plan family, tool version, model ID, time and redacted error. Do not send API keys, authorization headers, private code or full conversations.