Anthropic
Anthropic's Claude models are supported natively by TokenSense — no OpenAI translation layer needed. This page covers setup and supported models.
Connect Anthropic to TokenSense
Already have a TokenSense account? Here's how to start tracking Claude costs:
Step 1: Go to your dashboard → Provider Keys → Add your Anthropic API key.
Step 2:In your workflow, point requests at your TokenSense endpoint. Use Anthropic's native Messages API format — TokenSense handles it directly without translation.
Step 3: Authenticate with your TokenSense API key. Requests are forwarded to Anthropic and costs appear in your dashboard within seconds.
Native API support.TokenSense speaks Anthropic's Messages API natively. Your workflows don't need to translate to OpenAI format — use Claude exactly as Anthropic documents it. This means fewer integration headaches and accurate token counting.
Supported models
All pricing is per 1 million tokens (USD).
| Model | Input (per 1M tokens) | Output (per 1M tokens) |
|---|---|---|
| claude-opus-4-7 | $5.00 | $25.00 |
| claude-opus-4-6 | $5.00 | $25.00 |
| claude-sonnet-4-6 | $3.00 | $15.00 |
| claude-opus-4-5 | $5.00 | $25.00 |
| claude-sonnet-4-5 | $3.00 | $15.00 |
| claude-haiku-4-5 | $1.00 | $5.00 |
Legacy models
These models are still supported for cost tracking but are being phased out by Anthropic.
| Model | Input (per 1M tokens) | Output (per 1M tokens) |
|---|---|---|
| claude-opus-4-1 | $15.00 | $75.00 |
| claude-opus-4-0 | $15.00 | $75.00 |
| claude-3-5-sonnet-20241022 | $3.00 | $15.00 |
| claude-3-5-haiku-20241022 | $0.80 | $4.00 |
| claude-3-opus-20240229 | $15.00 | $75.00 |
Using Anthropic in your workflows
TokenSense works with any tool that can make HTTP requests:
n8n: The TokenSense n8n node supports Claude natively. Select an Anthropic model in the node configuration.
Make / Zapier: Use an HTTP module pointed at your TokenSense endpoint. Send requests in Anthropic's native Messages API format. See the Make & Zapier guide.
Custom code: Replace https://api.anthropic.com/v1 with your TokenSense endpoint. See the API reference.