---
title: How to Save Tokens on the Claude API
description: "Cut Claude API costs with prompt caching, the right model per task, and tighter context. Practical token-saving tactics that stack with the apiToken.sale discount."
url: https://apitoken.sale/docs/learn/save-tokens-on-claude-api
language: en
---

# How to save tokens on the Claude API

Your discount lowers the price per token; these tactics lower the number of tokens. Together they compound into a much smaller bill.

## Use prompt caching

Long, stable context — system prompts, large files, tool definitions — should be cached. Cache reads cost a fraction of fresh input tokens, so repeated context becomes cheap.

## Pick the right model

Do not send every request to Opus. Route cheap or high-volume work to Haiku, keep everyday coding on Sonnet, and reserve Opus for genuinely hard reasoning.

## Trim context

- Send only the files and history a task actually needs.
- Summarize long threads instead of resending them in full.
- Cap max_tokens to what the response really requires.

## Frequently asked questions

### What is the single biggest token saver?

Prompt caching for large, repeated context, combined with choosing the cheapest model that can do the job.

### Do these tips stack with the discount?

Yes. The discount lowers price per token; these tactics lower token count, so the savings multiply.

---
Get a key: https://apitoken.sale/register
More guides: https://apitoken.sale/docs/learn