Anthropic API and Crypto: How to Buy Claude API Credits with USDT or USDC

Anthropic sells Claude API access as prepaid credits that you buy with a card on the Claude Console, and crypto is not among the payment methods it lists. Anthropic's pricing FAQ says major credit cards are accepted for standard accounts, and enterprise customers can arrange invoicing. To pay with USDT, USDC or SOL, you load a card from your wallet and buy credits with that card.

This guide is about the API side only: Console credits, auto-reload, usage tiers, and Claude Code on API billing. If you want a Pro or Max subscription on claude.ai, read how to buy Claude with crypto instead.

1. Get a card that works on Anthropic's checkout, such as SolCard's Virtual for AI & Ad Spend ($10 to issue, 5% per top-up).
2. Top it up with USDT, USDC or another supported coin. Load more than the credits you plan to buy, because Anthropic adds applicable taxes on top of the credit amount.
3. Sign in to the Claude Console with an Admin or Billing role, open the Billing page (platform.claude.com/settings/billing), add the card, click Buy credits and enter an amount.
4. The credits are available right away, according to Anthropic's billing article. Create an API key, or sign in to Claude Code with the same Console account.

Anthropic emails a receipt for every purchase with the subject line "Your receipt from Anthropic", and the same receipts sit under Invoice history on the Billing page, per its invoices article.

There are two ways an organization pays for the API. Anthropic says most organizations use the first.

Source: How do I pay for my Claude API usage?

A few rules about prepaid credits catch people out, and all of them come from Anthropic's own pages:

• They expire one year after purchase, and the date can't be extended (billing article).
• They are non-refundable and non-transferable. The Credit Terms say credits can't be sold or moved to another account, and they also expire if you close the account.
• You pay only for successful calls. Failed requests aren't charged, but a request that was on track to succeed is still charged if your client disconnects or times out partway through.
• Purchased credits cover the API, the Console playground and Claude Code.
• All payments are in USD (pricing page).

Buy what you expect to use within the year. A large balance bought on a whim and left idle simply expires.

The pricing FAQ answers the payment-method question in two sentences: major credit cards for standard accounts, and invoicing or other methods for enterprise customers.

That leaves out several things people search for:

• Crypto. Not listed for the API, the Console or any Claude plan we could find.
• App store billing. Apple and Google can bill a Claude subscription bought in the mobile app, but API credits are bought on the Console in a browser. The app-store route that works for Pro does not exist for the API.
• Bank transfer. Only for organizations on a sales-arranged invoice.

So the practical answer to "how do I pay Anthropic with USDT" is the same as for any merchant that only takes cards: convert at the card, not at Anthropic.

Every API organization sits in a usage tier, and the tier caps how much it can spend each calendar month, whatever the credit balance. Anthropic's rate limits page says organizations are placed in a tier automatically, based on usage history and account standing, and move up over time. New organizations may start in an Evaluation tier with lower limits.

Source: Rate limits

Two consequences for anyone funding the API from a wallet:

1. More credits don't buy a higher cap. A $2,000 balance on a Start-tier organization still stops at $500 of usage that month. To go higher, use Request tier increase on the Console's Rate limits page.
2. Hitting the cap looks like a rate limit. The API returns HTTP 429 with the error code enforced_spend_limit_reached, with no retry-after header, and access resumes at 00:00 UTC on the first of the next month. Retrying does nothing.

You can also set your own lower spend limit on the Billing page. When you hit that one, requests fail with HTTP 400 instead.

Auto-reload buys credits for you when the balance runs low. On the Billing page you set two numbers, per Anthropic's billing article:

• When credit balance reaches: the balance that triggers a purchase.
• Bring credit balance back up to: the balance to refill to.

If your balance is already at or below the trigger when you switch it on, you're charged immediately to bring it up to the target, plus applicable taxes. The Credit Terms describe it as a standing authorization to charge your saved payment method for the credits and taxes on each reload, until you turn it off. Each reload gets its own receipt.

With a bank credit card, a reload just adds to your statement. With a prepaid card, the card has to hold the money at the moment the reload fires. If it doesn't, the charge is declined, no credits are added, and your API calls stop once the balance reaches zero.

The arithmetic is simple. Say you set the trigger at $20 and the target at $120:

Keep at least one full reload, plus tax, on the card at all times, and top it up again after each reload goes through. If you run agents overnight, keep two.

One more interaction to know about. Max, Ultra and Team plans include monthly API credits, and the Console spends those first. Anthropic's subscriber credits page says auto-reload watches only your purchased balance, so a reload can fire while included credits remain.

Claude Code runs on either a Claude subscription or Console credits. Anthropic's authentication docs list a Claude Console login as the route "for organizations that prefer API-based billing". Admins invite people from the Console's Members page and can give them a Claude Code role, which can only create Claude Code API keys.

Things worth knowing before you put Claude Code on credits:

• Purchased credits pay for it. Anthropic's billing article says purchased credits cover Claude Code.
• Included plan credits don't. The monthly API credits that come with Max, Ultra and Team can't be used in Claude Code, per the same article.
• An API key wins over a subscription login. If ANTHROPIC_API_KEY is set and you approve it, Claude Code bills that key instead of your plan. Run unset ANTHROPIC_API_KEY to go back, and /status to check which one is active (authentication docs).
• Usage scales with the work. A subscription has a flat price; credits drain per token. Set a workspace spend limit in the Console if several people share one organization.

If you'd rather pay a flat monthly price for Claude Code, a Pro or Max plan is the simpler route; our Claude post covers buying those with crypto.

When a crypto-funded setup breaks, it is usually billing, not the model. The first four causes come from Anthropic's pages; the last is what a declined reload leads to.

Sources: billing article, rate limits.

If a card charge itself is declined at checkout, check the card's balance first. Then check that you're on a card that works on Anthropic's checkout (see the SolCard section below).

The API is only offered in the countries and regions on Anthropic's supported regions list, and the same list covers claude.ai, Claude Code and Claude through cloud platforms. The policy applies to where you are physically located and to where your organization is incorporated or headquartered. A card funded with crypto doesn't change any of that, so check the list before you buy credits.

Anthropic adds applicable taxes to credit purchases, and auto-reload charges include them. Its billing address article says that for self-serve API organizations, the billing address is taken from your payment method and decides how tax is calculated. A business that needs a fixed address for VAT can ask Anthropic support to lock one, with documentation such as a VAT registration certificate. What you owe or can reclaim depends on where you are; ask a tax professional.

The Anthropic API is the largest merchant on Virtual for AI & Ad Spend, measured by our own payment data from mid to late October 2026. About 4 in 5 Anthropic charges on that card have gone through. That is a good rate for a prepaid card at an AI checkout, and it also means about 1 in 5 doesn't, so keep a buffer and don't rely on a single top-up the night before a deadline.

What it costs and what it doesn't do:

• $10 to issue, 5% per top-up. $100 of credits takes $105 of crypto, plus any tax Anthropic adds.
• Top up with USDT, USDC, USDG, EURC, ETH, BNB, POL, AVAX, HYPE, wBTC, wETH or SOL.
• Prepaid. It holds a balance you load from your wallet. There is no credit line behind it, which is exactly why auto-reload needs headroom.
• Use this card for the Console. In our data, SolCard's Platinum and Virtual cards don't get through on Anthropic's own checkout.

If you also pay other model providers, the same card is also used for OpenRouter credits; our OpenRouter payment guide covers its fees and auto top-up. For how developers spread infrastructure spend across providers, see how developers pay for cloud with crypto. New to SolCard? What is a crypto debit card explains how a wallet-funded card works.

Not directly. Anthropic's pricing FAQ lists major credit cards for standard accounts and invoicing for enterprise customers; crypto is not on the list. You can load a crypto-funded card with USDT, USDC or SOL and buy Console credits with that card.

Sign in to the Claude Console with an Admin or Billing role, open the Billing page at platform.claude.com/settings/billing, click Buy credits and enter an amount. Credits are available immediately and expire one year after purchase.

Only through a card. Load USDT or USDC onto a card such as Virtual for AI & Ad Spend ($10 to issue, 5% per top-up), then add that card on the Console Billing page. Anthropic sees a card payment in USD.

Yes, as long as the card holds enough when the reload fires. Each reload brings the balance back up to your target, plus taxes, so a reload set from $20 to $120 needs about $100 plus tax on the card. If the card is short, the charge is declined and your calls stop at $0.

Yes. Purchased credits expire one year from the purchase date, the date can't be extended, and all credit purchases are non-refundable. Monthly API credits included with Max, Ultra and Team expire at the end of each billing cycle.

Your organization has probably reached its usage tier's monthly spend cap: $500 on Start, $1,000 on Build, $200,000 on Scale. The error code is enforced_spend_limit_reached and access resumes at 00:00 UTC on the first of the next month. Request a tier increase on the Console's Rate limits page to lift it sooner.

Yes. Log in to Claude Code with a Claude Console account, or set an API key, and usage is drawn from purchased credits. The monthly API credits included with Max, Ultra and Team plans can't be used in Claude Code.

Paying for the Anthropic API with crypto is a card problem, not a crypto problem. The Console takes cards, bills in USD, and needs money on the card at the exact moment a purchase or reload runs. Treat the card like a float: size it to one or two reloads plus tax, refill after each one, and watch your tier's spend cap, because more credits won't raise it.

• How do I pay for my Claude API usage?, Anthropic Help Center
• Understanding your Claude API invoices, Anthropic Help Center
• Understanding your billing address and tax calculation, Anthropic Help Center
• Pricing, Claude Platform docs
• Rate limits, Claude Platform docs
• API credits for Max, Ultra, and Team plans, Claude Platform docs
• Authentication, Claude Code docs
• Supplemental Credit Terms, Anthropic
• Supported Regions Policy, Anthropic