How to check your Claude usage: claude.ai, Claude Code and the API

By NeverPayTwice · November 16, 2026 · 5-minute read

Short answer: it depends on how you pay. On a Claude plan, look at Settings > Usage on claude.ai, or run /usage in Claude Code. On the API, open the Usage and Cost pages in the Claude Console.

None of these is a per-conversation token counter. Below: what each screen shows, what it leaves out, and how to get a record of every response if you need one.

On claude.ai and the desktop app (Pro, Max, Ultra)

Open Settings > Usage. Anthropic's help page says you can see "how much you've used and the time remaining under Current session" there, along with your next weekly reset time.

What moves the bar, according to the same page: the length and complexity of your conversations, the features you use (tools and connectors are token-heavy), which model you chat with, and the effort level. Long chats cost more per message because the model rereads the whole conversation on every turn, so starting a new chat once the old context no longer matters is the simplest way to use less.

In Claude Code

Run /usage at the Claude Code prompt. What you see depends on how you signed in:

Two limits on those numbers, both stated in Claude Code's documentation:

Other places to look while you work:

On the API (Claude Console)

API usage is pay-as-you-go, and the Console is the authoritative record:

Both are visible to the Developer, Billing and Admin roles. Anthropic's article notes one gap: these pages can't break usage or cost down by individual user.

On a Team or Enterprise plan

Admins get a spend report in the organization's analytics with estimated spend per user and per model, exportable as CSV. The report covers usage credits; usage inside the seat allowance isn't metered in dollars. Each member's allowance resets on a five-hour window and a weekly window, shared with Claude chat.

What none of these screens give you

For Claude Code there is a local source you can read yourself: the logs in ~/.claude/projects record the usage block of every response. Adding those up directly over-counts, because the same response is written more than once. Why Claude Code token counts come out wrong explains the fix, and the free counter does it in your browser without uploading anything.

Free one-page checklist: AI API bill checklist (PDF), ten checks to print or share.

A record of every request, kept for you

NeverPayTwice is a small app we make. It reads your Claude Code logs and counts each response once, and its live meter keeps a receipt for every API request you route through it (Anthropic, OpenAI, Google Gemini and compatible APIs): time, model, request ID, tokens and cost. It flags requests you paid for twice. It never blocks or changes a request, nothing is uploaded, and API keys are never stored. Mac, Windows or Linux, $9 one time.

See it with sample data first, no sign-up.

Try the demoGet NeverPayTwice · $9

Sources, checked November 16, 2026: Claude Help Center, How do usage and length limits work? and Cost and usage reporting in the Claude Console; Claude Code documentation, Manage costs effectively. Screens and limits change; check the current pages.