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

How to use Codex CLI through the router's responses endpoint with Freellmapi

Point Codex CLI at the /v1/responses surface so it runs on free-tier models.

Authorization notice. Freellmapi is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA developer who uses Codex CLI for terminal coding help and wants to test it without a paid model subscription.

The problemCodex CLI needs the Responses API surface, which most free-tier wrappers do not offer.

The outcomeCodex CLI sends its requests to the router's /v1/responses endpoint and gets answers from the free pool.

What you need first

  • Node 20 or newer, or Docker for the one-liner install
  • API keys from one or more free-tier providers (for example Google, Groq, Cerebras, Mistral, OpenRouter)
  • A machine that can run the router on localhost:3001

Steps

  1. Install and start the router, then add provider keys and copy the unified key from the Keys page.
  2. Set Codex CLI's base URL to http://localhost:3001/v1 and use the unified key as its API key.
  3. Check your Codex CLI config file for the base URL and key fields and update them. (inferred, check the README)
  4. Run a short Codex CLI task in a test directory.
  5. Check the router dashboard to confirm the request was logged.

Prompt for your agent

In the freellmapi repo (tashfeenahmed/freellmapi), configure Codex CLI in <project-path> to use http://localhost:3001/v1 with the unified key from the Keys page. Expected output: Codex CLI completes a small task. Verify that the router logs a /v1/responses request.

Caveat. The README names /v1/responses as what Codex CLI needs, but the exact Codex CLI config keys are not documented here, so the config step is inferred.

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