Skip to content

Add Teapot Router as a provider (Anthropic + OpenAI dual-protocol gateway) #13486

Open

Description

@teapotrouter

Problem

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
  • Keys are created at https://teapotrouter.com

Offer

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions