Skip to content

Add BitRouter provider#2754

Open
SPIKESPIGEL404 wants to merge 1 commit into
anomalyco:devfrom
SPIKESPIGEL404:add-bitrouter-provider
Open

Add BitRouter provider#2754
SPIKESPIGEL404 wants to merge 1 commit into
anomalyco:devfrom
SPIKESPIGEL404:add-bitrouter-provider

Conversation

@SPIKESPIGEL404

Copy link
Copy Markdown

What

Adds BitRouter as a provider. BitRouter is an OpenAI-compatible LLM gateway, so it uses the generic @ai-sdk/openai-compatible package — no new SDK dependency.

name = "BitRouter"
env = ["BITROUTER_API_KEY"]
npm = "@ai-sdk/openai-compatible"
api = "https://api.bitrouter.ai/v1"
doc = "https://docs.bitrouter.ai"

Models

50 models, mirrored from the live https://api.bitrouter.ai/v1/models catalog:

  • 46 factored onto existing canonical base_models, overriding only [cost] and [limit] with BitRouter's live pricing/limits (same pattern as providers/kilo / providers/anyapi).
  • 4 standalone where no canonical base exists yet (deepseek/deepseek-v3.2, openai/gpt-oss-120b, x-ai/grok-4.1-fast, x-ai/grok-4.20).

Reasoning

Each model declares [interleaved] field = "reasoning_content". Verified live against the gateway: BitRouter normalizes upstream reasoning traces to the reasoning_content field on the Chat Completions envelope (both streamed output and replayed back on input), which matches the openai-compatible reasoning path.

Validation

bun run validate passes.

BitRouter (https://bitrouter.ai) is an OpenAI-compatible LLM gateway.

- provider.toml: @ai-sdk/openai-compatible, BITROUTER_API_KEY, api.bitrouter.ai/v1
- 50 models mirrored from the live https://api.bitrouter.ai/v1/models catalog,
  factored onto existing base_models where available (4 standalone where no
  canonical base exists yet).
- reasoning_content surfaced via [interleaved]; verified live against the gateway.
@SPIKESPIGEL404 SPIKESPIGEL404 force-pushed the add-bitrouter-provider branch from caad606 to 6f969c1 Compare June 23, 2026 19:35
@rekram1-node

Copy link
Copy Markdown
Collaborator

AUTOMATED REVIEW: Blocking merge: add the provider logo; add explicit provider-specific reasoning_options to every reasoning model; refresh prices against the live catalog; and factor Grok 4.20 through canonical base_model. The public mutable catalog should also have a sync implementation.

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.

2 participants