Integration guide
apifare for OpenAI Codex CLI
Give OpenAI Codex CLI one prepaid key for every API it needs. There is no separate provider account or provider API key for eligible capabilities, and it all runs under hard caps and a kill switch.
1 · Get a key
Create an account at /start: email in, token out (shown once). Save the token somewhere safe.
2 · Add apifare to OpenAI Codex CLI
Run this once. It writes an [mcp_servers.apifare] table to ~/.codex/config.toml, which the Codex CLI, the Codex IDE extension, and the ChatGPT desktop app share.
codex mcp add apifare --env APIPAY_TOKEN=<your-token> -- npx -y apifare-mcpReplace <your-token> with your token. Check it with codex mcp list, then start codex. Inside Codex, /mcp shows your active servers.
3 · Try it
Ask OpenAI Codex CLI to search the web for X, then to fetch a URL, then what's the weather in London. Every call is debited from your balance and lands on your signed, exportable audit chain.
4 · Stay in control
Set daily or monthly caps per agent, and keep the kill switch ready. Both are checked before a call is dispatched. When the balance runs out, your agent gets an HTTP 402 with a top-up link it can hand you; the error catalog lists every stop and what unblocks it.
What OpenAI Codex CLI can call
Everything on the key: search, filings, registries, weather, and ready-to-run tools, plus any provider key you vault yourself. Exact per-call prices are on /capabilities.
Config checked against OpenAI Codex CLI's MCP docs on 2026-09-12. Markdown version: /integrations/codex.md.
More integrations
Claude Code · Claude Desktop · Cursor · Windsurf · Zed · Cline · GitHub Copilot (VS Code) · Gemini CLI · Hermes Agent · Kimi CLI · Qwen Code · LibreChat
Model guides
Calling a model's API directly instead? Give it apifare tools with a plain tool loop: DeepSeek · Kimi · Qwen · OpenAI GPT · Gemini.