Codex vs OpenRouter: tracking usage on Mac and Windows

This is not an argument about which tool writes better code - that depends on your work, and anyone claiming otherwise is guessing. It is about something narrower and more answerable: how each one is metered, and what you can actually see while you use them.

How each is tracked

Codex uses an existing local login, and usage is read locally, so it keeps working when the network does not.

OpenRouter uses an OpenRouter API key, and it fronts many upstream models, so per-model spend is the easiest thing to lose track of.

How Codex and OpenRouter meter your usage

Codex can be paid for in two ways, both described on OpenAI's Codex pricing page. A ChatGPT plan (Go at $8 a month, Plus at $20, Pro at $100, $200 or $500) gives you an allowance: OpenAI estimates 15-160 local GPT-6.1 Sol messages per five-hour period on Plus, Pro plans currently have no five-hour limit, and weekly limits may also apply. An API key instead runs Codex in the CLI, SDK or IDE extension without the cloud features, with model availability following your key and usage charged at API pricing.

OpenRouter has no usage windows. You buy credits in US dollars and each request's token cost is deducted; per OpenRouter's FAQ, provider prices pass through with no markup on inference, and OpenRouter earns its fee when you buy credits. The pricing page puts that fee at 5.5% of each credit purchase on pay-as-you-go Standard and 8% on Business, while the Free plan covers 25+ free models at 50 requests a day.

OpenRouter's limits documentation names two kinds of ceiling. Credit limits (your balance, plus any cap you set on a key) return a 402 error; rate limits return a 429. Paid models pass through the upstream provider's rate limits, and free model variants allow 20 requests a minute and 50 a day, or 1,000 a day once you have bought at least $10 of credits. A key's credit cap can be set to reset, and its usage counters run per UTC day, week (starting Monday) and month.

For visibility, OpenAI points to the Codex usage dashboard for current limits and reset times, and to /status during a CLI session. OpenRouter's Activity page breaks spend, requests and tokens down by model, provider, API key, app or user, and GET /api/v1/key returns a key's remaining credit and usage.

At the limit, Codex lets an active turn keep working, subject to fair use, then you wait for the reset, buy credits on Plus or Pro, or switch to an API key at standard rates. OpenRouter returns a 402 for any request your balance or key cap cannot cover until you top up (by hand or with auto top-up) or raise the cap, and it reserves the right to expire unused credits a year after purchase. Plans and limits checked 3 October 2026 on each vendor's official pages.

Why this matters if you run both

Running two tools means two places to check, two sets of limits, and two chances to be surprised mid-task. The cost is rarely the money - it is losing your thread because something stopped answering and you did not see it coming.

Watching both in one place

SessionWatcher shows Codex and OpenRouter together in the Mac menu bar or the Windows taskbar. It reads and displays usage on your Mac or PC; it does not read your code or your conversations. That boundary matters more when you are pointing one tool at two providers.

Per-tool detail is in the Codex tracker guide and the OpenRouter tracker guide.

Frequently asked questions

Can I track both at once?

Yes - both appear in the same reading, in the Mac menu bar or the Windows taskbar.

What does each need?

Codex uses an existing local login. OpenRouter uses an OpenRouter API key.

Does it read my code?

No. Usage only, never code or conversation content.

Can I run Codex through OpenRouter?

Yes. OpenRouter's Ori Harness starts the Codex CLI with OpenRouter credentials through ori codex, and --model picks any OpenRouter model. That traffic is paid through normal OpenRouter billing and appears in its activity reporting; there is no separate Ori bill.

What happens when I run out on Codex versus OpenRouter?

Codex lets the active turn keep working, subject to fair use; then you wait for the reset, buy additional credits on Plus or Pro, or run extra local chats with an API key at standard API rates. OpenRouter rejects requests your credits cannot cover with a 402 error until you add credits, by hand or with auto top-up, or raise the key's credit limit.

SessionWatcher

Running both?
Watch them in one menu bar.

Native app for the Mac menu bar and the Windows taskbar. Track Claude, Codex and 20 more tools' usage, costs, and rate limits in real time.

★★★★★Trusted by developers daily
nicojerome

“Fast, simple, and does exactly what it should. Definitely worth it.”

@nicojerome on GitHub

Download Free for Mac

macOS 14+. Free for 7 days, no credit card.