Skip to content

docs: Starveri custom OpenAI-compatible gateway example (#66) - #76

Merged
doramirdor merged 1 commit into
mainfrom
docs/starveri-provider-example
Jun 30, 2026
Merged

docs: Starveri custom OpenAI-compatible gateway example (#66)#76
doramirdor merged 1 commit into
mainfrom
docs/starveri-provider-example

Conversation

@doramirdor

Copy link
Copy Markdown
Collaborator

Closes #66.

Adds docs/providers/starveri.md — a worked example of routing NadirClaw at a third-party OpenAI-compatible gateway, using Starveri as the concrete case, plus a link from the README's custom-endpoint section.

What's in the doc

  • The four env vars (NADIRCLAW_API_BASE + NADIRCLAW_SIMPLE_MODEL / NADIRCLAW_MID_MODEL / NADIRCLAW_COMPLEX_MODEL).
  • A copy-pasteable ~/.nadirclaw/models.local.json snippet with the current /models prices and a "verify against the live endpoint — prices drift" caveat.
  • Neutral framing ("example, not an endorsement; Starveri is operated independently from OpenAI").
  • Caveats that cached-input and per-tool fees are not modeled by the current cost_per_m_input / cost_per_m_output schema, and that it's prepaid-credits, not a permanent free provider.
  • A short verification checklist (smoke-test each tier; confirm the savings report picks up the local metadata).

Why this shape

Per the triage on #66: a docs example is welcome, but per-provider metadata baked into the repo is not — third-party gateway pricing drifts faster than the release cadence, so models.local.json (user-controlled freshness) is the right home. No code change — this is configuration users already control.

🤖 Generated with Claude Code

Adds docs/providers/starveri.md — a worked example of pointing NadirClaw
at a third-party OpenAI-compatible gateway, using Starveri as the concrete
case. Covers the four env vars (NADIRCLAW_API_BASE + the per-tier model IDs)
and a copy-pasteable models.local.json pricing override, with neutral
framing and caveats about price drift and unmodeled cached-input/tool fees.

No code change — this is configuration users already control. Per the
triage discussion on #66, per-provider metadata stays out of the repo
(it drifts faster than our release cadence); models.local.json is the
right home for it.

Links the new page from the README custom-endpoint section.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@doramirdor
doramirdor merged commit 44ec152 into main Jun 30, 2026
3 checks passed
@doramirdor
doramirdor deleted the docs/starveri-provider-example branch June 30, 2026 10:42
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.

Provider/model metadata request: Starveri API as a custom OpenAI-compatible endpoint

1 participant