DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to send your own app's Anthropic API calls through the pool with Claude Unlimited

Point any Messages API client at the local daemon so its requests use the pooled accounts.

Credentials. Your app authenticates to the local daemon with a placeholder token, so keep the daemon's dashboard and config files private to your machine.

Who it is forA developer building an app or script that calls the Anthropic Messages API and wants requests to survive a usage limit.

The problemA custom app that calls one account directly fails when that account hits its limit.

The outcomeThe app sends requests to 127.0.0.1 and the daemon picks the account for each request.

What you need first

  • Python 3.10+, git, and the claude CLI on your PATH
  • At least two accounts to pool: Claude Pro or Max, ChatGPT/Codex, or Anthropic API keys
  • A browser to complete the account login
  • macOS is the most tested platform; Windows and Linux are best-effort per the README

Steps

  1. Install the daemon and add your accounts as described in the README.
  2. Set the environment variable ANTHROPIC_BASE_URL=http://127.0.0.1:4317 in the shell that runs your app.
  3. Run your app as usual so its Messages API calls go through the daemon.
  4. Check the dashboard at http://127.0.0.1:4317/ to confirm the requests are counted.

Prompt for your agent

Using the DevDock-AI/claude-unlimited repo, set ANTHROPIC_BASE_URL=http://127.0.0.1:4317 and run <app-command> against the Messages API. Expected output: the app gets normal responses. Verify that the request appears in the dashboard activity log at http://127.0.0.1:4317/.

Caveat. The README describes this route for Anthropic-API clients but does not list every client that has been tested, so check your app's behavior first.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page