Summary

This project provides a toolset for automating the registration of ChatGPT/Codex accounts and generating OAuth tokens. It targets users who need to programmatically create multiple accounts or manage API access, leveraging the DuckMail API for email services and supporting output formats compatible with CLIProxyAPI v6. The primary benefit is streamlining the account creation and token generation process, which can be complex and manual otherwise.

How It Works

The toolset consists of two main scripts. chatgpt_register.py utilizes the DuckMail API to create temporary email accounts and then proceeds with the standard ChatGPT registration flow. The codex/protocol_keygen.py script further automates the Codex protocol's OAuth login process, exchanging credentials for refresh and access tokens. These tokens are then formatted into JSON files compatible with CLIProxyAPI v6, facilitating programmatic access to Codex services.

Quick Start & Requirements

• Installation: Requires bash and pip. Install dependencies using pip install curl_cffi requests urllib3.
• Prerequisites: A functional HTTP/HTTPS proxy is mandatory for registration, OAuth, and automatic token refreshes.
• Configuration: Copy config.example.json to config.json and codex/config.example.json to codex/config.json. Populate these files with DuckMail API credentials (base URL, bearer token), proxy details, and desired account parameters (e.g., total_accounts).
• Execution: Run python chatgpt_register.py for account registration and python codex/protocol_keygen.py for OAuth token generation.
• Links: DuckMail API reference is included in duckmaildoc.md.

Highlighted Details

• Automated registration and OAuth token generation for ChatGPT/Codex.
• Integration with DuckMail API for temporary email services.
• Outputs Codex auth files compatible with CLIProxyAPI v6.
• Supports optional uploading of tokens to a CPA management interface.

Maintenance & Community

No specific details on contributors, sponsorships, or community channels (like Discord/Slack) are provided in the README.

Licensing & Compatibility

The README does not explicitly state a software license. Compatibility for commercial use or closed-source linking is undetermined without a specified license.

Limitations & Caveats

A working proxy is strictly required for all core functionalities. Configuration files (config.json, codex/config.json) are intended for local use only and must not be committed to version control. Users are advised to securely store generated token JSON files, especially if utilizing CLIProxyAPI.