wtf is grok-build-auth?

grok-build-auth is a research client that reproduces the public web sign-up and login flow for x.ai's Grok service using plain HTTP requests instead of a browser. It walks through account creation with email verification, single sign-on, an OAuth PKCE exchange for the Grok Build access scope, and finally writes out a local authentication file formatted to work with a separate tool called CLIProxyAPI. The README states clearly, in a prominent notice, that the project is for authorized research use only: your own accounts, legal CTF competitions, in-scope authorized bug bounty targets, or academic protocol study. It explicitly prohibits fraud, mass account creation for resale, unauthorized targets, and deliberately violating a platform's terms of service, and it states the maintainers take no responsibility for how the tool is used. Running it requires Python 3.9 or newer, an API key for a Turnstile solving service compatible with the createTask protocol, and either a temporary email API key or a self hosted email alias setup using Cloudflare. An HTTP proxy and a local install of CLIProxyAPI are optional. The main script can register one or more accounts, run the OAuth exchange either serially or with limited concurrency, and export the resulting access and refresh tokens into a local JSON auth file that CLIProxyAPI can load. The project is explicit that it depends on undocumented, third party endpoints that can change or break at any time, and that the maintainers have no obligation to keep it working. It also notes that completing the OAuth step is required to produce a usable auth file. A single sign-on session alone is not enough. The repository is licensed under MIT, but the author stresses that the license does not remove legal responsibility from the person running the tool, and that unclear cases should be checked with a lawyer or the target platform's security team before running anything.