Skip to main content
Compare X (Twitter) API pricing and X API pricing with Xquik. Read the X (Twitter) API alternative and pricing guide. This page covers Xquik API pricing for tweet search and follower exports. It covers replies, profiles, timelines, monitors, webhooks, and write actions. Account workflows spend shared credits. Plans grant monthly credits that carry over. Guest wallets prepay the eligible paid-read routes. MPP pays per request on fixed-price operations.

Subscription

Starter

USD 20/month. Includes 140,000 monthly credits (USD 0.00014/credit). Prototyping and low-volume integrations. Monitor slots are unlimited.

Pro

USD 99/month. Includes 770,000 monthly credits (USD 0.00013/credit). Production workloads and growing teams. Monitor slots are unlimited.

Business

USD 199/month. Includes 1,670,000 monthly credits (USD 0.00012/credit). High-volume automation and enterprise use. Monitor slots are unlimited.
Higher tiers give you more credits at a lower per-credit cost. PAYG credits cost USD 0.00015 each.All tiers support unlimited monitor slots. Active monitors cost 30 credits per hour and check every second. The rate includes stored events and webhook delivery.Subscribe from the dashboard billing page. Plans activate immediately, renew monthly, and grant credits. Metered calls need enough available credits, not an active plan. Guest wallets and MPP provide accountless reads.

Pick a billing path by job

Use these cards to estimate the cost of an X API task. Do it before you run the task.

Search tweets to CSV or JSON

Use GET /x/tweets/search for a page of tweets or extractions for exportable jobs. Each tweet returned or extracted costs 1 credit.

Export followers

Use Follower extraction for CSV, JSON, or XLSX exports. Use GET /x/users/{id}/followers for paginated API reads. Each follower returned costs 1 credit.

Post tweets or replies

Use Create tweet. Send public media URLs in media when posting media. A text-only post costs 30 credits. Attached media adds 2 credits per started MB.

Upload media for DMs

Use Upload media when a DM needs an uploaded media_id. Each media upload call costs 10 credits.

Monitor tweets to webhooks

Use account and keyword monitors for tweet alerts and signed webhooks. Each active monitor costs 30 credits per monitor-hour, or 720 credits per day.

Recover from 402

Inspect payment_options. Ask the user to choose and confirm. Account, guest, and anonymous callers receive different payment choices. A key that reads only gets the account page instead.

Monitor pricing

Account monitors and keyword monitors use the same active billing rate.

Account monitor slots

Account monitor slots are unlimited. Active account monitors bill only while enabled.

Keyword monitor slots

Keyword monitor slots are unlimited. Active keyword monitors use the same hourly rate.

Active monitor hour

Each active monitor costs 30 credits per monitor-hour.

Check interval

Active monitors check every 1 second.

Webhook and event delivery

Active monitor billing includes webhook and event deliveries.
Creating or reactivating an account monitor requires at least 30 available credits. They pay for the first active monitor-hour, and the username lookup is free. Creating or reactivating a keyword monitor also requires at least 30 available credits. It then bills 30 credits per active monitor-hour.New active monitors are due for billing immediately. The create response includes nextBillingAt. After a successful hourly charge, the next billing time advances by 1 hour. Hourly billing may not find enough credits. The monitor may then pause until credits are available.Use GET /account to inspect current monitor billing. monitorsUsed includes active account monitors and active keyword monitors. So do monitorBilling.activeHourlyBurn and monitorBilling.activeDailyEstimate.

Plan monitor credits before you monitor tweets

Use GET /account before creating more tweet monitors or tweet alerts. Each active account monitor or keyword monitor adds 30 credits to monitorBilling.activeHourlyBurn. It also adds 720 credits to monitorBilling.activeDailyEstimate.

1 active monitor

The hourly cost is 30 credits. The daily estimate is 720 credits. Keep at least 30 credits before creating or reactivating one more monitor.

5 active monitors

The hourly cost is 150 credits. The daily estimate is 3,600 credits. Keep at least 30 credits before creating or reactivating one more monitor.

10 active monitors

The hourly cost is 300 credits. The daily estimate is 7,200 credits. Keep at least 30 credits before creating or reactivating one more monitor.
The account API returns the daily estimate for capacity planning. It is 24 hours of the hourly burn. If creditInfo.balance is below the next hourly burn, top up before enabling more monitors.

Monthly credits & carry-over

Every paid subscription invoice adds the monthly credit grant to your account balance. Subscription, top-up, and automatic top-up credits stay in that balance until you spend them.
  • All metered operations deduct from a single shared pool
  • No separate buckets per operation type
  • Unused subscription credits carry over to the next billing period
  • Rate limits also apply to API calls, separately from credit usage
  • When the shared balance reaches 0, metered calls return 402 Payment Required. See error handling for recovery patterns
  • Reading and managing stored monitor records, stored events, webhooks, and account endpoints are free. Active monitors bill hourly.
402 response body
Warning. Xquik rejects metered calls when available credits cannot cover the operation. Top up credits or subscribe to continue.
A caller on a plan that renews gets top-up only, plus credits_renew_at.
402 response body on a plan that renews
A caller whose plan payment failed gets top-up only. The message reads “Your plan’s payment failed. Update your payment or top up to keep reading.” When the balance hits 0 while reads continue, Xquik emails the account. It sends at most 1 such email per 7 days, in the account’s language.

Per-operation costs

Each metered operation deducts credits from your shared pool. Per-credit cost depends on your plan. It ranges from USD 0.00012 (Business) to USD 0.00015 (PAYG).

X sign-in fee

A write signs in to your X account only when no working session exists. It signs in again when X refuses the session of a sent write. That sign-in costs 10 credits, or USD 0.0015 at the PAYG rate.
  • Xquik first checks that your credits cover the sign-in and the write. If they don’t, you get 402 with no sign-in and no charge.
  • Xquik charges the 10 credits before the sign-in starts.
  • A sign-in that fails gets its 10 credits back.
  • A sign-in that works keeps its fee, even if the write then fails.
  • A write needs 2 sign-ins at most.
  • billing.chargedCredits on the write leaves the fee out, since it’s a separate charge.
  • Connecting or reconnecting an X account never charges it, and reads never do.

Extractions & draws

Extractions consume 1 or 5 credits per result depending on the extraction type.

Tweet-style results

1 credit per result. Includes tweets, replies, quotes, mentions, posts, likes, media, and search exports.

People results

1 credit per result. That covers followers, following, favoriters, retweeters, and community members. It also covers people search, list members, list followers, and verified followers.

Article results

5 credits per result. Applies to article extractions.
Draws charge for the source tweet lookup and the reply search. They charge for retweeter profile checks when mustRetweet is true. With mustFollowUsername, they charge 1 credit per follow check. That check runs on each author who passes the other filters. The draw first checks that the minimum cost is affordable. Remaining credits cap how many replies and retweeters the draw can inspect. Filters and winner selection run after that. The API may fail to deduct the final computed cost. It then returns 402 insufficient_credits and stores no draw result.

Credit-affordable result pages

Some paid X (Twitter) read endpoints charge per returned result. They treat limit, pageSize, count, and multi-ID request sizes as upper bounds. The remaining balance may not cover the full requested page. The endpoint can then return fewer results than requested. If zero paid results are affordable, it returns 402 insufficient_credits.

Free operations

Xquik charges no credits for stored monitor management, stored event reads, or webhook operations. It charges none for extraction and draw reads or exports. It charges none for cost estimates, composition, cached styles, drafts, support, or API keys. It charges none for X account management, credit top-ups, account status, or Radar. Active monitors cost 30 credits per hour.

Credit top-ups

Ask the user to confirm before you create account checkout. Do the same before you charge a saved payment method.
  • Use the top-up endpoint to create a checkout redirect after confirmation
  • Use the top-up status endpoint to poll checkout completion
  • The dashboard uses quick top-up for saved methods
  • Configure automatic top-up from the dashboard. GET /credits and GET /account return its enabled status and dollar amount. They also return its trigger threshold.
  • Automatic top-up stops after 3 declined charges in a row. The dashboard then asks you to update the card. A new card, a paid top-up, or a paid plan renewal restarts it. GET /credits reports the stop as auto_topup_stopped. GET /account reports it as creditInfo.autoTopupStopped.
  • Top-up credits cost USD 0.00015 each and reach your balance immediately
  • Top-up credits do not expire and carry over between billing periods
Example. Starter tier (USD 20, 140K credits). A USD 10 top-up adds 66,666 credits at USD 0.00015 per credit. Xquik rounds down to whole credits.

Recover from 402

An account 402 creates no checkout. Keep the failed request and get the user’s confirmation before billing. A full key’s 402 lists payment_options. A key that reads only gets no checkout actions. Its next_step sends the user to /dashboard/account instead.
  1. Check the current balance.
  1. After confirmation, create a checkout top-up when no saved payment method is available.
The dashboard can charge a saved method after confirmation. Only charged grants credits. It opens checkout for declined or no_payment_method.

Accountless guest wallets

Guest wallets prepay the eligible paid-read routes without an account. The user first confirms USD 10 to 250. POST /api/v1/guest-wallets then creates a one-use hosted checkout and returns a paid_reads key. Creation does not charge. The key stays inactive until Xquik verifies payment. A guest 402 offers only POST /api/v1/guest-wallets/topups. See the guest wallet guide.

Pay-per-use (MPP)

Fixed-price read operations accept direct MPP payments. You need no subscription. Media downloads require full account authentication because they create account-tied gallery links.

MPP per-call pricing

Use MPP overview for the complete list. Direct MPP uses fixed charge pricing.

USD 0.00015 units

GET /x/tweets/{id}, GET /x/tweets/{id}/translation, GET /x/tweets/{id}/embed, and GET /x/users/{id} cost USD 0.00015 per call. GET /x/followers/check, GET /x/spaces/{id}, GET /x/spaces/{id}/replay, GET /x/broadcasts/{id}, and GET /x/communities/{id}/info cost USD 0.00015 per call.

USD 0.00075 calls

GET /x/articles/{tweetId} costs USD 0.00075 per call.

USD 0.00015 trends

GET /trends and GET /x/trends use flat charge intent pricing.

Fixed charge intent

Every direct MPP operation advertises one fixed charge offer per request.

Checking usage

Call GET /api/v1/account to see your credit balance, lifetime usage, and monitor billing.
Response.
The creditInfo.balance field shows how many credits remain. The automatic top-up fields show whether top-up is enabled. They also show the charge amount and the balance threshold. At 0, Xquik rejects metered calls until you top up credits.
Tip. Poll the account endpoint on a schedule to track usage. Alert when creditInfo.balance drops below 20% of your plan’s monthly credit grant. Then you can top up before credits run out.

See what a read charged

Every answer to a read carries X-Xquik-Credits-Charged, the credits that request charged.
  • A filtered list charges only the rows it returns.
  • It is 0 for a page a filter empties. It is 0 for a page sent again too.
  • A write names its charge in billing.chargedCredits.

Cap spending per API key

Give each API key a monthly credit budget with monthlyBudgetCredits. Set it when you create a key or update one. The budget covers REST, MCP and Apify Actor calls that use the key.
  • monthlySpentCredits on each key shows its spend this UTC calendar month.
  • At 80%, Xquik sends the account owner 1 warning email per key each month.
  • Calls running at once can’t take the key past its budget.
  • A call that doesn’t fit what’s left gets 403 api_key_budget_reached and costs nothing.
  • A refused call never runs.
  • A read with a limit needs that many results’ price left.
  • A media download needs the price of every post it names.
  • A read without a limit returns only what fits. An extraction, a draw and a style refresh do the same.
  • A write needs its price plus 20 credits left, enough for 2 X sign-ins. It charges only what it uses.
  • A started call bills what it delivered, even past a lowered budget.
  • Raise or remove the budget to unblock the key. Or wait for the next UTC month.
A budget never changes what a call costs. It only stops calls that don’t fit.

Cancel renewal & request a refund

Open subscription settings, select Manage Plan, and cancel in the hosted billing portal. Cancellation stops future renewals. Access continues through the paid period. Unused credits remain usable after the plan ends. Cancellation does not issue a refund. Charges are non-refundable unless law or Xquik states otherwise. Review the Terms or contact support.

FAQ

What happens when I run out of credits?

Account and guest credit failures return 402 with credential-specific payment choices. Anonymous non-MPP paid reads return 401 with a Bearer challenge and guest wallet action. The direct MPP reads return 402 with a Payment challenge and the same action. No error creates checkout or charges a payment method.

Do unused credits carry over?

Yes. Subscription credits and top-up credits stay in the shared balance until you spend them.

How do I check my credit balance?

Call GET /api/v1/account. The creditInfo.balance field shows remaining credits.

Next steps

  • Get Account is the full account endpoint reference with response schema.
  • API Overview covers the base URL, authentication, rate limits, and conventions.