Which Twitter API accepts crypto payments?

#Does the official X API accept crypto?

No. The official X API sells pay-per-use credits that you buy upfront in X's Developer Console, and every payment rule on X's pay-per-use pricing page (opens in a new tab) is written around a card: auto-recharge "requires a saved payment method", and the welcome bonus goes to your first eligible payment card. Crypto, stablecoins and wallets appear nowhere in X's billing docs.

X's free credit rules (opens in a new tab), changed on October 13, 2026, add a detail that matters if you hold crypto. Credit and debit cards earn the one-time $20 credit after a first purchase; prepaid cards don't, although X still lets them pay. A card you load with USDT or USDC can buy credits, and if X reads it as prepaid, it earns no bonus.

Whichever card pays, the price stays X's: $0.005 per post read, $0.010 per profile or follower, and a cap of 3M post reads per monthly billing cycle, past which X sells only Enterprise contracts. The account comes first, too: a developer account opened with your X login, an app and an OAuth token. Our X API pricing breakdown lists every rate.

X Premium, the subscription for X accounts, is a separate product with its own checkout: paying for it buys no API credits.

#How to pay for Twitter data with crypto on Sorsa API

Sorsa API, a Twitter (X) API and scraper, takes crypto for its plans: you pay once for a month, a year or several months ahead, and nothing renews on its own. The account needs no card, no X developer account and no X login, so the whole route from sign-up to a paid plan runs without a bank.

1. Start free. Sign up and copy your API key from the dashboard. It already carries 100 free requests, enough to read up to 10K tweets, so you can test the endpoints you need before you spend any crypto.

2. Make a first request. Send your key in the ApiKey header. POST /search-tweets (opens in a new tab) takes X's search operators, reaches back to 2006 and returns about 20 tweets per request, each with its author's full profile.

   curl -X POST "https://api.sorsa.io/v3/search-tweets" \
     -H "ApiKey: YOUR_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"query": "stablecoin payments lang:en", "order": "latest"}'
   

3. Choose Crypto in Billing. Open Billing in the dashboard, pick Monthly or Yearly, and press Crypto on the plan you want.

4. Send the payment. The crypto checkout opens in a new window with the amount to send. The plan starts as soon as the network confirms the payment, and the dashboard updates by itself.

5. Pay ahead when you like. Buy more months before the current ones run out, or add funds to a pay as you go balance with crypto, from $10. That balance never expires and keeps calls running when a month's requests are spent.

6. Watch the paid period from code. GET /key-usage-info (opens in a new tab) returns the requests left on your key and valid_until, the date they expire. It never counts against your requests, so a script can call it before every job.

   import requests
   from datetime import datetime, timezone
   
   r = requests.get(
       "https://api.sorsa.io/v3/key-usage-info",
       headers={"ApiKey": "YOUR_API_KEY"},
       timeout=30,
   )
   r.raise_for_status()
   usage = r.json()
   ends = datetime.fromisoformat(usage["valid_until"].replace("Z", "+00:00"))
   days = (ends - datetime.now(timezone.utc)).days
   print(f'{usage["remaining_requests"]} requests left, {days} days to go')
   

   const res = await fetch("https://api.sorsa.io/v3/key-usage-info", {
     headers: { ApiKey: "YOUR_API_KEY" },
   });
   if (!res.ok) throw new Error(`HTTP ${res.status}`);
   const usage = await res.json();
   const days = Math.floor((Date.parse(usage.valid_until) - Date.now()) / 864e5);
   console.log(`${usage.remaining_requests} requests left, ${days} days to go`);
   

   {
     "key_requests": 100000,
     "remaining_requests": 73140,
     "total_requests": 126860,
     "valid_until": "2026-12-02T00:00:00Z"
   }
   

A 403 means the key has no requests left or the paid period has ended. A 429 means more than 20 requests in one second on that key: wait a second and send it again.

Good to know

Send the amount the checkout shows, on the network you picked. A crypto payment is final and the network fee is yours, so spend the 100 free requests on your real workload first and pay for the plan that fits it.

#What a crypto payment buys on Sorsa API

A crypto payment buys the same plan a card does: every endpoint, 20 requests per second per API key, and the plan's full quota, refreshed each month. Larger plans cost less per request, and a year costs ten monthly prices on every plan.

• Starter

  Requests a month

  10K

  Paid for a month

  $49

  Paid for a year

  $490

  Tweets by ID, per 1,000

  $0.049

• Pro

  Requests a month

  100K

  Paid for a month

  $199

  Paid for a year

  $1,990

  Tweets by ID, per 1,000

  $0.020

• Growth

  Requests a month

  250K

  Paid for a month

  $475

  Paid for a year

  $4,750

  Tweets by ID, per 1,000

  $0.019

• Enterprise

  Requests a month

  500K

  Paid for a month

  $899

  Paid for a year

  $8,990

  Tweets by ID, per 1,000

  $0.018

The per-1,000 column assumes POST /tweet-info-bulk (opens in a new tab), which returns 100 tweets per request. Above 500K requests a month, the high-volume plans run from 1M to 10M requests and bring tweets down to $0.014 per 1,000 and followers to $0.007.

Pick a plan and how far ahead to pay, and the planner shows the one payment it takes.

Monthly requests don't pile up. Each month starts with the plan's full quota, and requests you didn't use lapse when the month ends, the same as on a card plan. The 100 free requests are the one exception: they never expire.

#Crypto or card: what changes on Sorsa API

Only the billing changes: a card plan renews until you cancel it, while a crypto plan runs for the months you paid and then stops. The data, the speed and the price per request are the same.

Side by side, the two differ only in how you pay, renewal and cancelling; the quota, the balance, the endpoints and the speed match.

• How you pay

  Paid with crypto

  Once, for a month, a year or several months ahead

  Paid by card

  A subscription, monthly or yearly

• Renewal

  Paid with crypto

  None; a reminder arrives before the plan ends

  Paid by card

  Automatic until you cancel

• Cancelling

  Paid with crypto

  Nothing to cancel

  Paid by card

  Anytime in Billing; the plan runs to the end of the paid period

• Monthly quota

  Paid with crypto

  Full each month, refreshed monthly

  Paid by card

  Full each month, refreshed monthly

• Pay-as-you-go balance

  Paid with crypto

  Top up with crypto from $10

  Paid by card

  Top up by card from $10

• Endpoints and speed

  Paid with crypto

  All 45, 20 requests per second

  Paid by card

  All 45, 20 requests per second

You can move from crypto to a card subscription whenever you like, for example when a team wants renewals to run without anyone sending a payment.

#Three ways to pay for Twitter data with crypto, compared

Crypto can reach Twitter/X data three ways, and they differ in what the payment buys and what each tweet then costs.

• A crypto-funded card on the official X API. You load a card with crypto and X charges it like any card. Everything else stays as it was: the developer account, OAuth, and X's per-item prices.
• Crypto top-ups and per-call payments. Some third-party APIs take crypto only to add credits to a balance, while their monthly subscriptions take cards alone, and a few take USDC per request from a wallet through the x402 protocol.
• A plan paid with crypto. On Sorsa API one payment covers a month or a year of requests at the plan's own price, with no card anywhere in the chain.

The first route is the one most "pay X with USDT" guides describe, and it keeps X's prices. The cards below put a month of tweet reads on each side.

Before you send crypto anywhere, check six things: what the payment buys, the price per 1,000 items, renewal, setup, what it asks of your X account, and how you can test first. Sorsa API meets each one with a number you can check on its pricing page.

• What the payment buys

  Sorsa API, paid with crypto

  A plan for a month to a year

  Official X API, crypto-funded card

  Prepaid credits, charged as a card payment

• Tweets, per 1,000

  Sorsa API, paid with crypto

  From $0.014

  Official X API, crypto-funded card

  $5.00

• Followers, per 1,000

  Sorsa API, paid with crypto

  From $0.007

  Official X API, crypto-funded card

  $10.00

• Renewal

  Sorsa API, paid with crypto

  None; a reminder before the end

  Official X API, crypto-funded card

  Auto-recharge needs a saved card

• Setup

  Sorsa API, paid with crypto

  One API key in a header

  Official X API, crypto-funded card

  Developer account, app and OAuth

• Your X account

  Sorsa API, paid with crypto

  Never asked for; read-only, so nothing posts

  Official X API, crypto-funded card

  X login opens the developer account

• Testing first

  Sorsa API, paid with crypto

  100 free requests, no card

  Official X API, crypto-funded card

  No free tier

The Sorsa API column holds on every plan, whether you pay with crypto or by card.

#Start free, then pay for the months you need

The official X API takes cards, so paying for Twitter data with crypto means a third-party API. Sorsa API takes crypto for whole plans, a month or a year at a time, with nothing renewing behind your back. Tweets cost from $0.014 per 1,000 and followers from $0.007, at 20 requests per second on every plan. Spend the 100 free requests on the calls your project makes, then send one payment for the months you plan to use.

#FAQ