docs(ai-gateway): document the new enabled field in GET /v1/models - #5552
Draft
bgrenon wants to merge 1 commit into
Draft
docs(ai-gateway): document the new enabled field in GET /v1/models#5552bgrenon wants to merge 1 commit into
bgrenon wants to merge 1 commit into
Conversation
The AI Gateway GET /v1/models response now returns an `enabled` boolean on every model entry, currently always true. Add it to the sample JSON on the models page and note what it reflects. Tracked in LKB-14983. Co-authored-by: omnigent <noreply@omnigent.ai>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Doc-only fix from the docs-drift audit: 1 correction in 1 file. Not auto-merged — awaiting your review.
The AI Gateway
GET /v1/modelsresponse now returns anenabledboolean on every model entry, but the sample response and field notes on the models page didn't mention it. This adds it.Add the
enabledfield to the model-list exampleBefore → After (sample JSON under "List available models"):
"id": "gpt-5-mini", "canonical_slug": "gpt-5-mini", + "enabled": true, "pricing": null,Plus one line of prose after the reserved-fields note:
Why the new text is right: a live
GET /v1/modelscall against a real branch returnsenabledon every entry, currentlytrue. See How to verify.Files
content/docs/ai-gateway/models.mdenabledto the sample/v1/modelsresponse and a one-line note on what it reflectsHow to verify
Create an
ai_gateway:invokecredential for a branch (Console → Credentials, or the API shown on the get-started page), then call the model list:Every object in
data[]includes"enabled": true. Verified against live Neon: all 42 returned models carried"enabled": true.Text-only change; no build or deploy behavior affected.
Scope / what's intentionally untouched
Only the
enabledfield is added. The other reserved OpenRouter fields (pricing,per_request_limits,context_length) and their existing "always null" note are unchanged.Tracked in LKB-14983.