Claude Haiku 4.5 Pricing: A Worked Monthly Bill on SwiftRelay

Cost per lapEN2026-11-02

Setting Up Claude Haiku 4.5 on SwiftRelay

Getting Claude Haiku 4.5 running through SwiftRelay is designed to be a short, practical setup. SwiftRelay is a pay-per-token API relay, so there is no monthly fee and nothing to subscribe to. You top up a balance, and each call deducts only what it used. That makes it easy to start with a small amount, watch the usage details, and decide how much to add next.

For this walkthrough, we will use Claude Haiku 4.5, listed on the SwiftRelay pricing page as claude-haiku-4-5-20251001. Its current price per 1M tokens is $0.3542 for input, $1.69 for output, and $0.0278 for cache read. The example below turns those prices into a worked monthly bill.

Claude models answer through the official Claude Code or Claude Desktop client, version 2.1.285 or later. In Claude Code, copy these three lines, with your own SwiftRelay key in place of the placeholder:

01  export ANTHROPIC_BASE_URL=https://api.fastapirelay.com
02  export ANTHROPIC_AUTH_TOKEN=<your swft_ key>

claude

That is the whole setup path: copy three lines and run. Your account supports up to 20 live API keys, and the dashboard usage list shows tokens and cost per call, so you can check the numbers as you work.

Reading Claude Haiku 4.5 Pricing Clearly

The useful part of per-token billing is that the bill follows actual usage. Claude Haiku 4.5 has three listed rates on SwiftRelay: $0.3542 per 1M input tokens, $1.69 per 1M output tokens, and $0.0278 per 1M cache read tokens. Input tokens are the tokens sent to the model, output tokens are the tokens returned, and cache read tokens are the listed cache-read category. You do not need to guess a fixed monthly charge.

Here is an example monthly usage pattern. Assume you make 10 calls a day for 30 days, giving 300 calls in the month. Each call uses 1,000 input tokens, 500 output tokens, and 200 cache read tokens. These are example assumptions, not a promise about how a particular project will behave.

Input: 300 calls × 1,000 tokens = 300,000 tokens. At $0.3542 per 1M tokens, the input cost is $0.10626.
Output: 300 calls × 500 tokens = 150,000 tokens. At $1.69 per 1M tokens, the output cost is $0.2535.
Cache read: 300 calls × 200 tokens = 60,000 tokens. At $0.0278 per 1M tokens, the cache-read cost is $0.001668.

Adding those three example amounts gives a monthly Claude Haiku 4.5 bill of $0.361428 on SwiftRelay. The calculation is simple because every line uses the same per-token prices. If your real calls are smaller or larger, the dashboard usage list gives you the tokens and cost per call, so you can replace the example assumptions with your own activity.

This is also a good moment to compare the approach with keeping your own subscription or official account in general terms. SwiftRelay does not sell a fixed monthly package; it charges for the tokens your calls use. A quiet month stays quiet, while a busier month reflects the extra work. You stay in control of the balance you top up.

Choosing a Top-Up and Watching the Balance

SwiftRelay offers top-up amounts of $1.39, $6.94, $13.89, $27.78, $69.44, and $138.89. Pick the amount that suits the pace of your example workload. If you begin with $1.39, the $0.361428 example bill leaves the remaining balance visible without committing to a recurring subscription.

New accounts also receive $0.22 in sign-up gift credit. That credit sits alongside the balance you choose, giving you a little room to make a first call and see the flow before adding more. Once calls begin, each one deducts only what it used.

The dashboard is the place to check the details. Usage lists tokens and cost per call, which lets you trace the example calculation back to individual requests. If a call used 1,000 input tokens, 500 output tokens, and 200 cache read tokens, those figures are the basis for its cost. There is no need to estimate from a monthly average when the per-call record is available.

Support is handled through Messages in the dashboard, and login is required. That keeps questions and account context in one place. If something about a call or a charge looks unfamiliar, you can open Messages and ask about the usage record instead of guessing.

Understanding Refunds and Referral Rewards

Because SwiftRelay uses pay-per-token billing, the refund rule is worth reading before you top up. Unused credit can be refunded within 11 days of a top-up, minus what was used and the payment fee. In other words, the amount that has already been consumed by calls is not part of the unused credit, and the payment fee is deducted as well.

You can also invite other people to top up. When someone you invited adds funds, you receive 14% of that top-up. From the people they invite, you receive 3%. Rewards can be withdrawn, with a minimum withdrawal of $4.86, or moved into your balance. Moving rewards into the balance is convenient when you want them available for the next Claude Haiku 4.5 call without a separate withdrawal step.

These two features fit together neatly. Top up an amount, run your calls, and use the usage list to see what each one costs. If the balance is getting low, add more. If you have invited others, the referral rewards can either join that balance or be withdrawn once the minimum is reached. SwiftRelay keeps the process visible rather than hiding it behind a plan.

Running the Example and Adjusting It

Let us walk through the example one more time as a quick pit-stop check. Start with the Claude Code configuration, copy the three lines, and run claude. Make the calls that your work requires, then open the dashboard usage list. You should be able to match each call's tokens and cost with the activity that produced it.

For the example pattern of 300 calls, the input line is $0.10626, the output line is $0.2535, and the cache-read line is $0.001668. Together, the monthly bill is $0.361428. If you make 20 calls a day instead of 10, the same calculation can be rebuilt from the new call count and token totals. The prices stay fixed on the pricing page while your usage changes.

Small adjustments are easy to make. Fewer calls reduce the number of requests. Shorter prompts reduce input tokens. Shorter answers reduce output tokens. Each change appears in the usage list, so you can see the effect rather than relying on a guess.

One important detail keeps the example clean: Claude Haiku 4.5 is used through the official Claude Code or Claude Desktop client, version 2.1.285 or later. SwiftRelay's Claude setup is not a general-purpose shortcut for unrelated clients. Keeping the client pairing correct means the configuration you copied is the configuration the model expects.

With a balance, a clear usage record, and no monthly fee, the monthly bill becomes a running total instead of a commitment. SwiftRelay is ready when you are, and the next run can start as soon as your first three lines are in place.

Start Your SwiftRelay Run Today

SwiftRelay makes it easy to try Claude Haiku 4.5 with pay-per-token billing, a worked monthly bill you can check, and a setup that takes three copied lines. Top up, run your calls, and see the cost per request in the dashboard.