Repository navigation
docs(guide): document Standard Compute as an openai_compatible provider example - #383
henrikdukefoss wants to merge 2 commits into
Conversation
…er example Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks for the PR and for disclosing your affiliation up front. A provider row is fine, and it matches the existing examples (#214, #217, #297). One change before merging, though, because it matters for how SkillOpt is used: SkillOpt's validation gate compares a baseline and a candidate skill on the same tasks, and results need to be reproducible across nights and reruns. A router model like Could you:
With that, happy to merge. |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks Yifan Yang (@Yif-Yang). Done in 13d5703: the table row now uses the pinned ID |
Summary
This PR adds Standard Compute to the
openai_compatibleexamples indocs/guide/new-backend.md.It is docs only.
It uses the same pattern as #297.
Standard Compute is an OpenAI-compatible LLM gateway. Its
StandardComputemodel sends each request to the cheapest enabled model that can handle it, with automatic fallback. Pinned model IDs come from the publicGET https://api.stdcmpt.com/v1/models.Disclosure: I work on Standard Compute.
Details
Changes:
Tests:
mkdocs build --strictflags anything.Usage:
🤖 Generated with Claude Code