Status
An endpoint’s status shows where it is in review and whether you’ve paused it.Availability
Once approved, an endpoint’s availability shows whether it’s serving traffic.How availability changes
- A new or edited endpoint starts as Pending validation and is tested shortly after approval.
- If every required check passes, it becomes Up. If a check fails, or the endpoint stays unreachable over repeated attempts, it becomes Rejected. Fix the problem and edit the endpoint to try again.
- An endpoint that’s up becomes Degraded after repeated failed requests. It returns to Up when test traffic succeeds.
- An endpoint that stays degraded for more than an hour, or fails a periodic re-check, becomes Down. It returns to Up when a re-check passes.
- Changing the URL, bearer token or upstream model name sends the endpoint back to Pending validation, because earlier results no longer apply.
Validation checks
The required check tests that your endpoint speaks the OpenAI protocol the way TokenChange needs:/v1/modelslists your upstream model name.- A short streamed chat completion with a fixed arithmetic question returns the correct answer in
delta.content. Reasoning fields are ignored. - The final usage chunk reports
prompt_tokens,completion_tokensandprompt_tokens_details.cached_tokens.
Read validation results
Open an endpoint from Provider > Endpoints:- Current results shows the latest run of each check for the current configuration.
- Validation runs lists every run, most recent first, with its result, trigger and when it finished.
GET /v1/provider/endpoints/{id}/validations.