Skip to content
English

Switch theme

Discover▾

Not sure where to start? This week’s hottest software, models and stacks in three minutes.

AI Apps▾

AI software people use: from assistants like ChatGPT to tools for coding, video and workflows, picked by purpose.

For Agents▾

Software for AI: tools that let your agent (Claude Code, Codex, Cursor…) browse, read docs, run code and remember.

Models▾

Choose models, estimate cost, self-host: prices, rankings, benchmarks, free tiers and compute.

Solutions▾

A goal or an error message? Ready-made stacks, steps and fixes by scenario.

Learn▾

A systematic course from zero to the frontier, with an algorithm library, must-read papers and tutorials.

Frontier▾

Daily AI news, weekly highlights, the latest papers and how AI is changing every discipline.

// How-to · Control AI costs and usage limits

How much have Claude Code / Codex used and cost?

Usage windows and limits on subscription tools are opaque, and API calls are scattered. Local log analysers and a unified gateway are the two main approaches.

verified 2026-10-102 official sources

Scenario: Control AI costs and usage limits →

Symptoms

  • You do not know how close you are to a limit and get throttled at bad moments
  • The monthly bill is higher than expected

Common causes

  • Subscription usage is only shown roughly in the official UI
  • Calls are spread across projects and keys with no aggregation

How to fix

  1. Subscription users: analyse local logs with ccusage, e.g. npx ccusage@latest (supported tools and commands per the project README)
  2. API users: route calls through a gateway such as LiteLLM or OpenRouter to see spend per key and project in one place
  3. Record tokens and cost per request with an observability tool such as Helicone
  4. Set usage alerts or hard caps in the provider’s console
  5. Limit rules change often; follow the latest official terms and note the date you checked

Official references

Compiled from official documentation and public discussions on 2026-10-10; not yet reproduced in our own environment. Follow the official docs if they differ.

Data updated: Problems & errors