Repository navigation
docs: add Standard Compute OpenAI-compatible gateway example - #527
henrikdukefoss wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
🔵 Needs a closer look
Provider compatibility remains unconfirmed because all three snippets use StandardCompute instead of the documented request ID standardcompute, and repository inspection cannot establish alias or case support.
No open issues 🎉
What changed in this PR
Adds Standard Compute as a concrete example of TypeChat’s existing OpenAI-compatible gateway support. The PR is documentation-only, with no library behavior changes or new dependencies.
Changes:
- Adds API key, model, and endpoint configuration examples to the examples guide and both language guides.
- Describes the gateway’s model routing and automatic fallback behavior.
| File | Description |
|---|---|
site/src/docs/typescript/basic-usage.md |
Adds Standard Compute configuration under OpenAI-compatible gateways. |
site/src/docs/python/basic-usage.md |
Adds the equivalent gateway configuration for Python users. |
site/src/docs/examples.md |
Adds a Standard Compute .env example for running the examples. |
Review effort: Balanced
|
henrikdukefoss please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
|
Thanks for the contribution and for disclosing your affiliation. We're moving gateway documentation toward vendor-neutral examples, including replacing the existing named examples, so we shouldn't add another provider listing. The goal is to explain how to use OpenAI-compatible endpoints, not to maintain a directory of commercial providers or imply an endorsement of their services. This applies consistently to the existing OrcaRouter/OpenRouter examples as well. I'll open a separate PR replacing those references with a fictional Adatum gateway and proposing an explicit non-goal for provider listings and promotion. Support for OpenAI-compatible gateways will remain unchanged. |
|
Superseded by #528 |
Motivation
TypeChat already supports OpenAI-compatible gateways through
OPENAI_ENDPOINTand theendpoint/endPointarguments, and the docs describe that pattern. This adds a concrete example for Standard Compute, an OpenAI-compatible gateway.Changes
site/src/docs/examples.md:.envexample for Standard Computesite/src/docs/typescript/basic-usage.mdandsite/src/docs/python/basic-usage.md: the same example under "Using OpenAI-compatible gateways"The example sets
OPENAI_ENDPOINT=https://api.stdcmpt.com/v1/chat/completionsandOPENAI_MODEL=StandardCompute. That model routes each request to the cheapest enabled model that can handle it, with automatic fallback.Notes
Documentation only. No library behavior changes and no new dependencies.
Disclosure: I work on Standard Compute.
🤖 Generated with Claude Code