FR: Add ChatGPT Translate as a provider

[theblazehen]

Feature Type

New provider

Description

I would like to have ChatGPT translate added as a provider. This should provide unlimited GPT-5.2 access.

Looking at the network calls on https://chatgpt.com/translate/, it seems pretty simple

Use Case

This would allow free GPT-5.2 access

Additional Context

No response

Pre-submission Checklist

• I have searched existing issues to ensure this is not a duplicate

[mirrobot-agent]

@theblazehen Thank you for submitting this issue. I am now beginning my analysis and will report back shortly.

[mirrobot-agent]

Initial Analysis Report

Summary: This is a feature request to add "ChatGPT Translate" as a provider to the LLM-API-Key-Proxy. The user suggests that this endpoint (https://chatgpt.com/translate/) might provide access to high-end models (referred to as GPT-5.2) and seems relatively simple to implement based on network call analysis.

Issue Validation: Confirmed (Feature Request)

Reproducibility Assessment: Not Applicable

Root Cause Analysis: The project currently supports a wide range of providers via LiteLLM and custom implementations (like gemini_cli and antigravity), but does not have a provider for OpenAI's web-based translation interface. Implementing this would require a custom provider class that mimics the network calls made by the chatgpt.com/translate page.

Suggested Labels: enhancement, provider

Proposed Next Steps:

1. Reverse Engineering: Perform a detailed analysis of the network traffic on https://chatgpt.com/translate/ to identify the underlying API endpoint, request/response format, and any necessary authentication (e.g., session tokens, cookies, or Cloudflare protection).
2. Implementation:
   • Create a new provider file: src/rotator_library/providers/chatgpt_translate_provider.py.
   • Implement ChatGPTTranslateProvider inheriting from ProviderInterface.
   • If the API is not OpenAI-compatible, implement has_custom_logic() returning True and provide a custom acompletion() method.
3. Integration: Update src/rotator_library/provider_config.py to include the new provider in the LITELLM_PROVIDERS list for TUI/CLI discovery.
4. Verification: Test the implementation with valid session credentials to ensure model access and rotation work as expected.

Missing Information (if any): While the user mentioned the network calls seem simple, providing specific details (sample request/response bodies, required headers) would significantly accelerate the initial implementation phase.

This analysis was generated by an AI assistant.

[Mirrowel]

That is a translator webpage. How would this provide unlimited 5.2?
There is also no real api there.

[theblazehen]

The translation method is just a gpt call with a "translate this please" system prompt, we should be able to make arbitrary requests by just changing the request? Might need to grab some headers from the browser though... After challenge auth

…

On Sat, 31 Jan 2026, 19:25 Mirrowel, ***@***.***> wrote: *Mirrowel* left a comment (Mirrowel/LLM-API-Key-Proxy#114) <#114 (comment)> That is a translator webpage. How would this provide unlimited 5.2? There is also no real api there. — Reply to this email directly, view it on GitHub <#114 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAY746QIBLYNXDDY5HUWDWD4JTQRNAVCNFSM6AAAAACTRII6YWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRYHA3DSOBVGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Mirrowel]

Hmm. Definitely low priority but worth researching potentially.