Repository navigation
docs: reference pages match the gateway users actually call (issue #68) - #74
Merged
Merged
Conversation
The rate-limit section states the real fixed caps (200/min per workspace, 500/min per IP, 10 in flight, identical on Cloud and self-hosted) and the throttle env rows are rescoped to the dashboard's own API calls. The glossary's last 424 goes. The tier and reason header rows document the values a client can receive — live-verified: a Manifest-answered request reports tier simple with model and provider manifest. The verbatim-forwarding claim becomes what Manifest does to the body. The Anthropic version header is accepted and ignored. A matching custom-tier header beats an explicit model ID, stated on the glossary, headers, and routing pages alike. Chat clients' 200-with- message delivery heads the status table, and the headers section stops promising every request.
This was referenced Aug 20, 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
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.
Applies the recommended options for all ten findings of #68 (batch pass, 2026-08-18), deduplicated against the already-merged PRs #62 and #65:
THROTTLE_*rows are rescoped to the dashboard's own API calls. When platform PR #2724 (env-configurable caps, still open) is merged and released, a follow-up documents the real overrides.2-3. 424 and the error envelope: the api.mdx and headers.mdx halves were already fixed by docs: llm-gateway and API reference drop the 424 myth (issue #53) #62; this PR fixes the glossary's last 424 and adds the provider-forwarded-429 clause to the status table.
X-Manifest-Tier: simplewith model and providermanifest, values the old rows said could not occur. Rows rewritten to the values a client can receive; the tier's name appears in the dashboard, never in a header.max_tokens, merges harness defaults, drops OpenAI-only fields outside OpenAI/OpenRouter routes.Also consumes the parked self-hosted.mdx line (drops "rate limits" from the optional-env list).
Coherence: GREEN. Closes #68.