SSD Nodes Learn 8GB RAM — $66/yr
Guides Matt ConnorBy Matt Connor

Does the Claude API have a free tier?

No free tier, a small credit at signup, and several parts that cost nothing at all. The July 2026 rates, plus a worked cost for a first small app.

Does the Claude API have a free tier?

The Claude API has no free tier. There is no monthly allowance of free tokens, and no plan you can sit on for $0. What a new account does get is a small amount of free credits to test the API, and Anthropic does not publish the amount. Once those credits are spent, every request draws on a balance you have paid for.

That is the direct answer. The rest of this guide is what follows from it: which parts of the platform cost nothing at all, why this is a different question from the free plan in the Claude apps, and the cheapest honest way to get a first program working.

What is free on a Claude API account

Several pieces of the platform carry no token charge, and they matter more than they sound.

  • Counting tokens. The token counting endpoint is free to use. It has its own requests-per-minute limit, separate from message creation, so measuring a prompt never eats into the budget for sending it.
  • The Console itself. Creating an organization, reading your usage page, and opening the Workbench cost nothing. Running a prompt in the Workbench is an ordinary API request, so that part bills tokens like any other call.
  • File operations. Uploading, listing and deleting files through the Files API is free. You pay only when a file's content enters a request as input tokens.
  • Web fetch. The web fetch tool adds no charge beyond the tokens of whatever it pulls into the conversation. Web search is not free: it is $10 per 1,000 searches as of July 2026.
  • Code execution, up to a point. Each organization gets 1,550 free container hours per month as of July 2026, then $0.05 per hour per container. Code execution costs nothing extra when it runs alongside web search or web fetch.

None of that is a free tier. It means the metering is honest: you are billed for inference, and not for the plumbing around it.

Price a prompt before you pay for it

Because counting is free, you can learn the exact size of a request first. This is the same endpoint the SDKs wrap, and it takes the same body as a real message.

curl https://api.anthropic.com/v1/messages/count_tokens \
  -H "x-api-key: $ANTHROPIC_API_KEY" \
  -H "content-type: application/json" \
  -H "anthropic-version: 2023-06-01" \
  -d '{
    "model": "claude-haiku-4-5",
    "system": "You are a scientist",
    "messages": [{"role": "user", "content": "Hello, Claude"}]
  }'

A healthy response is one line of JSON: {"input_tokens": 14}. Multiply that by your model's input rate and you know the cost of the request before you send it. If you get HTTP 401 with authentication_error, the key is wrong or revoked. Counting works even on an account with no credit left, because nothing is generated.

Why this is a different question from the free plan in the apps

People search for both, and the two have almost nothing to do with each other. The free plan on the Claude apps is a real product you can use for a long time without a card, metered by a rolling usage window, and what the Claude free tier actually includes covers what it carries and when it resets. The API is prepaid metering with no such plan behind it.

The consequence that trips people up is that a subscription and an API key are separate wallets. Paying for Pro does not fund a key, and API credits do not raise your chat allowance. If you are choosing between the two rather than trying to avoid paying at all, Claude API cost versus a subscription works through the arithmetic on real workloads.

What a request costs once the credits are gone

These are the first-party API rates as of July 2026, per million tokens.

ChartClaude API rates per million tokens, July 2026
The data behind this chart
[
  {
    "label": "Haiku 4.5",
    "input_usd": 1,
    "output_usd": 5
  },
  {
    "label": "Sonnet 5, intro rate",
    "input_usd": 2,
    "output_usd": 10
  },
  {
    "label": "Opus 5",
    "input_usd": 5,
    "output_usd": 25
  }
]

Haiku 4.5 bills 1 dollar per million input tokens and 5 dollars per million output tokens. Opus 5 bills 5 and 25 for the same volumes, so the model you pick moves a bill by 5x before any prompt tuning does. The Sonnet 5 figure is an introductory rate that runs to 31 August 2026, after which it returns to $3 and $15. Output costs five times what input costs on every one of them, which is the most useful fact on this page: a chatty answer is more expensive than a long question. which Claude model you should use compares them on a worked job.

The cheapest real paths to experiment

Four levers do almost all the work, and none of them needs a discount.

  • Start on the smallest model that passes your test. Classification, extraction, tagging and routing rarely need a frontier model. Haiku 4.5 is a fifth the price of Opus 5 and answers faster.
  • Cap max_tokens. It is a hard ceiling on generated tokens, and output is the expensive half. A classifier that answers in one word should not carry a 16,000-token budget.
  • Cache the part of the prompt that never changes. A cache read costs 10% of the base input price and a five-minute cache write costs 1.25x, so caching pays for itself after a single read. Caching is a prefix match, which means the stable text has to come first and the varying question last, or nothing matches and you pay the write premium for nothing.
  • Batch anything that is not interactive. The Message Batches API is 50% off both input and output, and most batches finish inside an hour. Nightly jobs, backfills and evaluation runs belong there.

A worked cost for a first small app

Take a log-summary script: 1,000 calls, each sending about 800 input tokens of log lines and getting back about 200 tokens of summary. That is 800,000 input tokens and 200,000 output tokens on Haiku 4.5.

Chart1,000 calls at 800 input and 200 output tokens, Haiku 4.5
The data behind this chart
[
  {
    "label": "Standard rates",
    "cost_usd": "1.80"
  },
  {
    "label": "Same job on the Batch API",
    "cost_usd": "0.90"
  }
]

The arithmetic is 0.8 million input tokens at $1 plus 0.2 million output tokens at $5, which is 1.80 dollars in total. Sent as a batch instead, the same work costs 0.90. A starter credit balance covers a lot of testing at that scale, which is why the absence of a free tier bites much later than people expect. For the full walkthrough on a server you own, building a first Claude API app on a VPS covers key handling, streaming and the error paths.

Usage tiers are ceilings, not allowances

The API places every organization on a usage tier automatically, based on usage history and account standing. The tiers are named Start, Build, Scale and Custom, and each one sets rate limits plus a monthly spend cap. As of July 2026 the caps are $500 on Start, $1,000 on Build and $200,000 on Scale, and Custom has no cap.

Read that as a limit rather than a grant. Being on the Start tier does not mean you have $500 to spend. It means you may not spend more than $500 in a calendar month before usage pauses until the next month. You can also set your own lower spend limit under the tier cap, which is the first thing to do on any account attached to a card, because a runaway loop is a far more common way to lose money than the per-token price is.

What to do if free is a hard requirement

If the budget is genuinely zero and has to stay there, the API is the wrong tool, and no amount of tier shopping changes that. Two honest options remain. Use the free plan in the Claude apps for interactive work, accepting that it is metered by window and gives you no programmable endpoint. Or run an open-weights model on hardware you rent, which swaps a per-token bill for a server bill you control: running Ollama on a VPS to self-host an LLM covers the memory each model size needs and what the small ones can actually do.

For anything in between, the practical answer is a funded key, a low spend limit, a small model, and prompt caching turned on from the first day.

FAQ

Is the Claude API free to use?

No. There is no free tier and no monthly free token allowance. New accounts receive a small amount of free credits to test the API, and after that every request draws on prepaid credit or a card on file. Some parts of the platform do cost nothing, including token counting, file uploads and deletions, and the web fetch tool beyond the tokens of what it fetches.

Do I get free credits when I sign up for the Claude API?

Yes, a small amount, and Anthropic does not publish the figure. Treat it as enough to prove your integration works rather than as a budget to build on. Extended trial credit for enterprise evaluation is arranged through Anthropic sales, not granted automatically.

Does paying for Claude Pro or Max include API access?

No. A subscription and an API key are billed separately and metered differently. Pro and Max raise your allowance inside the Claude apps. An API key draws on prepaid credits and is limited per minute by requests and by tokens. Needing both means paying for both.

What is the cheapest way to test the Claude API?

Count your tokens first, since that endpoint is free. Then run the test on Haiku 4.5 with a tight max_tokens, cache any fixed system prompt so repeat calls read at 10% of the input price, and send anything that is not interactive through the Batch API at half price. On those settings a thousand small calls costs a little over a dollar as of July 2026.