docs: add an Experimental page for direct completions - #54
Merged
Merged
Conversation
Give direct completions endpoints one visible Experimental page with a warning banner that states the current verification limitations: attestation reports cover only the answering instance, and signature lookups can return 404 on another instance. Link it from Private Inference (keeping the #direct-completions anchor) and from the Verification overview, and list it in a new Experimental navigation group.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
PierreLeGuen
changed the base branch from
codex/refresh-verification-docs
to
main
September 23, 2026 10:04
This was referenced Sep 23, 2026
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
1 participant
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.
Summary
Stacked on #49. That PR removes direct endpoints from onboarding and adds experimental direct verification pages, but nothing links to those pages, and the basic usage docs for direct endpoints are gone. Existing direct users would have no page that tells them how the endpoints behave today.
This PR adds one visible Experimental page:
cloud/experimental/direct-completions.mdx: a warning banner with the current verification limitations, the endpoint format and registry, a sample request, the route list, links to the experimental verification pages from docs: refresh Cloud verification guides #49, and steps to move to the Gateway.docs.json: a new "Experimental" group at the end of the Documentation tab that holds only this page.cloud/private-inference.mdx: a short "Direct Completions" section that points to the page. It keeps the old/cloud/private-inference#direct-completionsanchor working, which the integration guides linked to before docs: refresh Cloud verification guides #49.cloud/verification/index.mdx: a note that points direct-endpoint users to the page.Limitations in the banner
Checked against code and live endpoints:
all_attestationscontains only the report of the instance that answered: inference-proxy builds the response withvec![report]. Twelve concurrent TLS connections toglm-5-3-flash.completions.near.aipresented three different certificate keys, so a key pinned from one report fails on another instance. Tracked in Direct endpoints: return the complete serving model-attestation set cloud-api#1087.src/cache.rsin inference-proxy), so a lookup that reaches another instance returns404. The public registry atcompletions.near.ai/endpointslists onlydomainandmodels, so clients can't target an instance.Validation
mint validatepasses.mint broken-linkspasses.200fromglm-5-3-flash.completions.near.aiwithmodel: z-ai/glm-5.3-flash.The base is #49's branch. GitHub retargets this PR to
mainwhen #49 merges.