Jake Reinhold’s claudecookie.com turns three browser-oriented Claude cookie utilities into public HTTPS JSON endpoints: convert cookie formats, check a session, and generate the credentials file Claude Code reads. The API needs no key, but “no-key” does not mean “no risk”: the project says conversion happens in the browser, while checking and credential generation send cookie data to the service and Anthropic.
What problem the tools address
Reinhold describes the format gap this way: “the browser stores your login as a sessionKey cookie, but Claude Code wants ~/.claude/.credentials.json.” Claude Cookie tools are intended to bridge that gap and make related session tasks available both through a browser interface and from scripts.
![Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results](https://m.media-amazon.com/images/I/415+fSJacsL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
Convert cookie formats
The converter handles Netscape cookies.txt, Cookie-Editor JSON, Puppeteer format, key-value pairs, and a raw Cookie header. The project README says a conversion paste can contain up to 40 cookie sets. It describes conversion as client-side, so the cookie data stays in the browser for this operation.
Recommended Free Tools
Check a session
The check utility reports whether a session is active and displays account-plan information and usage windows. The README documents batches of up to 10 cookies in one request.
#1 Best Overall
Generate Claude Code credentials
The credential utility generates the ~/.claude/.credentials.json file Claude Code reads. It accepts one cookie set per request; the README says Free accounts cannot mint credentials.
How to use the browser interface or API
The project offers two ways to run the workflows. Use the browser interface for interactive paste-and-download work; call the JSON API when a script needs to automate a supported operation. Reinhold describes the API as HTTPS, public, and usable without an API key, with wildcard CORS.
| Workflow | Documented endpoint | Useful when | Data-flow note |
|---|---|---|---|
| Convert | POST /api/v1/convert |
You need to transform one or more cookie sets into a supported format. | README describes conversion as staying in the browser. |
| Check | POST /api/v1/check |
You need session status, plan information, or usage windows; batch size is up to 10. | README says the encrypted paste is sent to the service and Anthropic. |
| Generate credentials | POST /api/v1/credential |
You need a Claude Code credentials file from one cookie set. | README says the encrypted paste is sent to the service and Anthropic; Free accounts cannot mint credentials. |
The routes and workflow descriptions above are from Reinhold’s 2026 account and the project README. They identify the endpoints and constraints, but do not establish a particular request-body schema or response shape; consult the project’s current API documentation before wiring a client to them.
Published API limits
Reinhold published the following limits in 2026. They are project-documented limits, not independently load-tested measurements, and may change.
| Scope | Published limit |
|---|---|
All /api/v1/* routes |
10 requests per second per IP, with a burst allowance of 20. |
POST /convert |
60 requests per minute per IP. |
POST /check |
20 requests per minute per IP. |
POST /credential |
5 requests per minute and 20 per hour per IP; 3 per hour per sessionKey. |
A 429 response carries a Retry-After header whose value is the wait time in seconds. A script should respect that value rather than immediately retrying; requests still count against the documented limits.
What “no-key” does—and does not—mean
No API key lowers the setup friction for scripts, but it also means the documented controls are rate limits rather than per-user API credentials. The limits are scoped by IP and, for credential generation, by session key. The sources do not specify other access-control or abuse-prevention guarantees, so don’t infer them from the no-key design.
More importantly, these workflows do not all have the same data path. The README says the browser performs conversion locally. For check and credential generation, it says the browser encrypts the pasted cookie and sends it to the service and Anthropic. It also says credential tokens are not stored on the server and that responses are returned to the user. Those are project statements, not findings from an independent security audit; the service’s handling has not been independently verified here.
Free tools Windows power users keep installed
One-click scans. No signup required.
Handle the cookie as a credential
Reinhold’s warning is direct: “Treat a live session cookie like a password: only paste a session you control.” A live sessionKey or sessionKeyV3 can grant access to an account, so avoid putting it in public scripts, logs, shared terminals, or requests you do not trust. Use conversion locally when that is all you need; only send a live cookie through check or credential workflows if you accept the documented data flow.
Best Value
The project says it is independent and is not made by, endorsed by, or connected to Anthropic. Its availability, endpoint behavior, and implementation details should therefore be judged as those of a third-party service, not an official Claude or Anthropic feature.
Quick Recap
When the API is the right fit
- Prefer the browser interface for an occasional interactive conversion or download, especially if you do not need automation.
- Consider the API when a script needs repeatable JSON workflows and the documented limits and cookie transmission are acceptable.
- Keep conversion separate from session operations: the README describes conversion as local, but says checking and credential generation send data onward.
- Check current documentation first for request and response formats, supported behavior, and limits; the figures here are the developer’s 2026 published values.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
