Skip to content

docs(ai-gateway): document the new enabled field in GET /v1/models - #5552

Draft
bgrenon wants to merge 1 commit into
mainfrom
polly/lkb-14983
Draft

docs(ai-gateway): document the new enabled field in GET /v1/models#5552
bgrenon wants to merge 1 commit into
mainfrom
polly/lkb-14983

Conversation

@bgrenon

@bgrenon bgrenon commented Aug 16, 2026

Copy link
Copy Markdown
Collaborator

Doc-only fix from the docs-drift audit: 1 correction in 1 file. Not auto-merged — awaiting your review.

The AI Gateway GET /v1/models response now returns an enabled boolean on every model entry, but the sample response and field notes on the models page didn't mention it. This adds it.

Add the enabled field to the model-list example

Before → 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:

enabled reflects whether your account can use that model. It's currently always true while per-account access verification is off.

Why the new text is right: a live GET /v1/models call against a real branch returns enabled on every entry, currently true. See How to verify.

Files

File Change
content/docs/ai-gateway/models.md Add enabled to the sample /v1/models response and a one-line note on what it reflects

How to verify

Create an ai_gateway:invoke credential for a branch (Console → Credentials, or the API shown on the get-started page), then call the model list:

curl "$NEON_AI_GATEWAY_BASE_URL/v1/models" \
  -H "Authorization: Bearer $NEON_AI_GATEWAY_TOKEN"

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 enabled field 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.

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>
@vercel

vercel Bot commented Aug 16, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
neon-next Ready Ready Preview Aug 16, 2026 7:54pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant