mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-07-31 12:22:14 +03:00
2 lines
2.9 KiB
JSON
2 lines
2.9 KiB
JSON
{"author":{"id":"U_kgDOCx6-pA","is_bot":false,"login":"aartzz","name":"ArtZabAZ"},"body":"### Problem / Use Case\n\nOmniRoute currently supports API-key-based providers like OpenRouter and Ollama, but lacks integration for [t3.chat](https://t3.chat) — a popular multi-model AI platform by Theo Browne that provides access to 50+ models (Claude, GPT-4o/5, Gemini, DeepSeek, Grok, Llama, etc.) under a single $8/month subscription. Users who rely on t3.chat for cost-effective model access have no way to route those requests through OmniRoute's unified proxy, forcing them to manage a separate client and authentication outside of their existing infrastructure.\n\n### Proposed Solution\n\nAdd [t3.chat](https://t3.chat) as a new provider in OmniRoute. Due to the platform's architecture, this would likely require cookie/session-based authentication rather than a standard API key. Key implementation points:\n- Authenticate using convex-session-id and browser cookies _(similar to how unofficial clients like [T3Router](https://github.com/vibheksoni/t3router) and [t3-python-client](https://github.com/thethereza/t3-python-client) operate)_.\n- Support chat completions for major models.\n- Support model discovery/listing.\n- Handle session refresh automatically where possible.\n\n### Alternatives Considered\n\n- Using third-party reverse-engineered clients directly — this bypasses OmniRoute's routing, load balancing, logging, and rate-limiting features.\n- Using individual official APIs for each model provider — this requires managing multiple API keys and subscriptions, which defeats the cost-efficiency of [t3.chat](https://t3.chat).\n\n### Acceptance Criteria\n\n- [t3.chat](https://t3.chat) appears as a selectable provider in the OmniRoute dashboard.\n- Chat completion requests can be proxied to [t3.chat](https://t3.chat) successfully.\n- Available models are discoverable and listed.\n- Cookie-based authentication is configurable in provider settings.\n- Existing providers and integrations remain unaffected.\n\n### Area\n\nProvider Support\n\n### Related Provider(s)\n\nt3.chat\n\n### Additional Context\n\n- Pricing: $8/month Pro subscription _(free tier with limited models also exists)_.\n- Authentication: No official public API key; uses browser cookies + `convex-session-id`.\n- Reference implementations: [T3Router (Rust)](https://github.com/vibheksoni/t3router), [t3-python-client](https://github.com/thethereza/t3-python-client).\n\n### Expected Test Plan\n\n- Unit tests for the [t3.chat](https://t3.chat) provider adapter.\n- Integration tests for chat completion routing.\n- Verify model discovery endpoint.\n- Ensure no regressions in existing provider tests.","comments":[],"createdAt":"2026-05-03T09:19:28Z","labels":[{"id":"LA_kwDORPf6ys8AAAACYAlrLw","name":"enhancement","description":"New feature or request","color":"a2eeef"}],"number":1909,"title":"[Feature] add t3.chat web provider","url":"https://github.com/diegosouzapw/OmniRoute/issues/1909"}
|