You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add Teapot Router as a provider (Anthropic + OpenAI dual-protocol gateway) #13486
A number of Continue users arrive from the CLI agent world (Claude Code, Codex CLI) already holding a gateway API key, and the natural next question is "can the same key power Continue in my IDE?" Today the answer is "yes, but hand-write the provider block." A listed provider would remove that friction.
Request
Please consider Teapot Router as a listed provider option. It's a hosted gateway serving both API shapes from one key, pay-as-you-go:
OpenAI-compatible base: https://api.teapotrouter.com/v1 — /chat/completions and /responses both implemented
Anthropic Messages base: https://api.teapotrouter.com — so Claude models can run in their native protocol (incl. autocomplete/chat split by model)
Auth: Authorization: Bearer <key>
GET /v1/models returns the live model catalog (useful for model-name hints in the picker)
Machine-readable catalog JSON, public, same source as the website: https://teapotrouter.com/api/pricing
If maintainers are open to it, I'll submit the implementation under your normal contribution process — provider entry, default config block, and docs snippet. If you'd rather not add vendor entries, closing this is completely fine; the manual config path works today.
Disclosure: I operate Teapot Router (independent project — no affiliate or rev-share implied). Happy to answer questions here or at support@teapotrouter.com.
Activity