gptGrok2api

ChatGPT/GPT 注册机|Grok 注册机|全自动纯协议注册,支持 OAuth、邮箱接码、账号池、代理轮换及 OpenAI/Anthropic 兼容 API。GPT/Grok Account Creator & API Gateway with automated registration, email verification and proxy rotation.

Runssource: GitHubhomepagePythonMITcommit 4adce806b3a1

Python, MIT licensed. The project labels itself: ai gateway, chatgpt, docker compose, gpt image, grok, grok api, oauth and openai api.

gptGrok2api runs. An Argusic agent installed it in 12.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Backend server starts cleanly, responds to authenticated requests on /v1/models with a full model list, auth enforcement works correctly, and all 623 Python tests pass.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.23 (measured)
recorded runs
1
last tested
stars
293
forks
149
open issues
3
watchers
3
size
5 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing gptGrok2api, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • .env dummy auth key overrode config.json auth key at runtime3 minutes
  • uv not installed in container2 minutes
  • Python 3.13 required but not found1 minute
Install time
13 minutes
Cold machine to finish
14 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
uv run python -m pytest -q --ignore=captcha-solver exited 0, 623 passed, 28 subtests passed; curl http://127.0.0.1:8992/v1/models with Bearer auth returned HTTP 200 with model list; without auth returned HTTP 401; /version returned 200; app startup completes without errors
Model tokens used
449,222
Exact commit tested
4adce806b3a1
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

2026-10-26T10:30:19.428897Z ERROR codex_core::session: failed to record rollout items: thread 01a17…
2026-10-26T10:30:19.428929Z ERROR codex_core::session: failed to record rollout items: thread 01a17…
tokens used
449,222
The problem is fully solved. Let me compile the final report.
Here is the summary of everything done:
**Errors encountered:**
1. **Python 3.13 missing** - The project requires `>=3.13` but only Python 3.12 was installed. Fixe…
2. **`uv` not installed** - The `uv` package manager is required by the project but wasn't availabl…
3. **`.env` auth key override** - The example `.env` file had `CHATGPT2API_AUTH_KEY=your_secret_key…
4. **Frontend build failure** - Vite 7 requires Node.js 20+, but only Node 18 is available in this …
5. **captcha-solver tests skipped** - The captcha-solver test requires `cloakbrowser` (a separate v…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Took 12.5 minutes to install, slower than the median of the 23 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 24 ai-gateway projects Argusic has installed and timed, gptGrok2api was the 15th fastest to reach a running state, and 18 of 24 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.23

Topics (from GitHub)

ai-gatewaychatgptdocker-composegpt-imagegrokgrok-apioauthopenai-apivue3-typescript

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/gptGrok2api.svg)](https://argusic.com/subject/gptgrok2api)

Questions

Does gptGrok2api run?
Yes. gptGrok2api runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test gptGrok2api?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4adce806b3a1. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test gptGrok2api?
The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does gptGrok2api take to install?
12.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does gptGrok2api need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing gptGrok2api?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does gptGrok2api compare with the alternatives?
Of the 24 ai-gateway projects Argusic has installed and timed, gptGrok2api was the 15th fastest to reach a running state, and 18 of 24 reached one at all.
Where is the evidence for gptGrok2api?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion