By Sorsa Editorial

Updated June 2026: rewritten after X launched pay-per-use as the default model in February 2026 and changed its write and engagement pricing on April 20, 2026.

Key takeaway: No. The official X (Twitter) API has no free tier for new developers in 2026. Pay-per-use is the default: you buy credits upfront and pay per resource, with no free read allowance. The only free access left is X's program for verified public-utility accounts posting safety alerts.

If you need to read public X data, the practical question is not whether the official API is free (it is not) but what the cheapest reliable access actually costs. Sorsa API, an alternative Twitter/X API provider, starts at $49 a month for 10,000 requests, uses a single API key with no OAuth and no approval queue, and bills one request per call while bundling the author profile into every tweet response at no extra charge. The official API, by contrast, meters every post read at about $0.005 and every profile at about $0.010, with nothing free to prototype against.

On this page

Is the Twitter/X API free in 2026?

The Twitter/X API is not free in any practical sense in 2026. New developers are routed to a pay-per-use model where credits are purchased upfront in the Developer Console and deducted per request, with no free read allowance and no monthly minimum. A developer account is still required before any call.

According to X's developer pricing documentation, reads are billed per resource returned and writes are billed per request, with no subscription and no minimum spend. The "no monthly minimum" line is what creates the confusion: it means you owe nothing if you make zero calls, not that any calls are free. The moment you read a post you pay (about $0.005 per post, about $0.010 per profile or follower), and there is no included quota to build a prototype on.

So the honest framing is this: free to sign up, never free to pull data. For a deeper view of the rates and tiers behind that, see the full 2026 X API cost breakdown.

What happened to the old free tier?

The generous free Twitter API ended in February 2023, and what survived was reduced to a write-only stub before being folded into pay-per-use in February 2026. New developers can no longer select a standalone free tier at all.

Three changes reshaped access over three years:

  1. February 2023: X ended free access to the v2 and v1.1 APIs and introduced paid tiers. What remained "free" became a write-only path (a few posts per month, no usable reads).
  2. February 6, 2026: X launched pay-per-use as the default for new developers, after a closed beta that ran from around October 2025. The old fixed Basic and Pro subscriptions were removed for new signups and kept only as legacy options. Per X's pay-per-use launch announcement, recently active "Legacy Free" users were migrated onto pay-per-use with a one-time $10 voucher, and only "for-good" public-utility apps keep free scaled access.
  3. April 20, 2026: X restructured write and engagement pricing. Standard post creation rose to about $0.015, posts containing a URL jumped to $0.20, and follow, like, and quote-post write actions were moved to Enterprise-only.

The takeaway for anyone reading old guides: any article still describing a selectable "Free" tier with 1,500 posts a month as a current option for new accounts is out of date. That tier is now "Legacy" and closed.

Can you read or search tweets for free?

You cannot read or search tweets at any useful volume for free on the official API. The free access that historically existed was write-oriented, and the 2026 pay-per-use model charges for the first read with no free search quota included. Tweet search in particular has never been part of free access.

This is the gap between expectation and reality that drives the question in the first place. People expect a free tier like many other APIs offer, and instead find a path designed for posting bots, not data collection. Pulling timelines, running searches, mapping followers, monitoring mentions: all of it sits behind paid access or a third-party provider.

There is one genuinely free way to see what X data looks like without spending anything, and it does not involve the official API. You can test endpoints in a browser through a visual playground: run a profile lookup, a tweet search, or a follower pull and inspect the JSON, with no API key and no signup. Retrieving that data programmatically through the API does require a paid key, so this is a way to validate the data shape before committing, not unlimited free data.

Who still gets free X API access?

Free X API access in 2026 is limited to verified public-utility accounts: government and public-service entities posting safety information such as weather, transport, and emergency alerts. There is no free tier for general developers, businesses, students, or academic researchers.

The public-utility carve-out is the one exception X has kept consistently. Its February 2026 announcement reaffirmed that only "for-good" public-utility apps continue to get free scaled access, a policy that traces back to the 2023 pricing overhaul when X exempted verified accounts posting public-service alerts. If your use case is a transit agency tweeting service disruptions, you may qualify; almost nothing else does.

Academic access, often assumed to be free, is effectively gone. X closed the free Academic Research track to new applicants in 2023 and removed the academic API endpoints in June 2023. A narrow access path tied to the EU Digital Services Act exists for research into systemic risks, but reporting from researchers and outlets including Fast Company indicates very few applications have been approved, and rejected applicants are pointed to paid Enterprise access. Research groups that need historical data now typically pay pay-per-use rates or move to a third-party API; the practical options are laid out in our guide to accessing historical X data and on the API access for academic research page.

Are the "free" workarounds actually free?

The common "free" workarounds are free only in the sense that they have no licence fee. In practice each one carries real costs in setup time, proxy spend, breakage, and terms-of-service risk, which is why none of them is reliable for production work.

The two main categories:

Browser and library scraping. Tools like Playwright and Puppeteer are free in code but need residential proxies to get past X's Cloudflare protection and login wall, and IP blocks arrive within hours at any real volume. Among Python libraries, snscrape and twint are broken or archived (snscrape's maintainers paused development in 2023 and the library relies on endpoints X has since shut down), while Twikit and TweeterPy still work intermittently but break on every X frontend change and rotate-token update. All of these reverse-engineer X's internal endpoints, which violates X's terms of service and offers no SLA, no warning, and no migration path. We cover why these tools keep failing in our breakdown of open-source Twitter scrapers.

Third-party trial credits. Several data providers dangle a small free credit (a dollar or even ten cents) to start. It is real, but it is a sample, not a free tier: a few thousand calls that run dry mid-prototype, after which you pay per call anyway. Treat it as a test drive, not free access.

Undocumented internal or embed endpoints sometimes surface in tutorials too, but they return single public posts at most, not search or timelines, and can be rate-limited or changed without notice. For a fuller picture of the tradeoffs, see Twitter API alternatives.

The cheapest reliable way to get X data

For read-heavy work above roughly 10,000 reads a month, the cheapest reliable option is a managed read-only API with flat per-request billing rather than per-resource official pricing or fragile scraping. The economics flip in favor of a flat-rate provider as soon as read volume crosses that threshold.

Here is how the realistic options compare for someone whose goal is reading public X data on a budget:

ApproachCost to startFree read allowanceSetupRead and searchReliability
Official free tier (Legacy / public-utility only)$0None for new developersAccount plus approvalWrite-oriented, no usable searchNot viable for data
Official pay-per-useBuy credits upfront, no minimumNoneDeveloper account, OAuth 2.0About $0.005 per post, $0.010 per profileHigh, first-party
DIY scraping (Twikit, Playwright)$0 in code, plus proxy costNot applicableAccounts, residential proxiesFull but fragileBreaks on UI changes, ToS risk
Flat-rate managed APIFrom $49 a monthFree playground UI to test (API needs a key)Single API key, ~3 min, no approvalFlat per request, profile includedManaged, 99.9% uptime

For reading public X data on a budget, the official free tier gives nothing usable and pay-per-use has no free allowance, so the real choice is DIY scraping (cheap to start, expensive to maintain) or a managed read API with predictable pricing. If you need to post, send DMs, or sign first-party data agreements, that is the official API's territory; for read-heavy access at a flat, predictable price, a managed alternative is the stronger fit.

Where a managed alternative wins is on the exact axes that hurt on the official path: cost, setup, and authentication. Billing is one request per call regardless of how many records come back, follower and batch endpoints return up to 200 profiles or 100 records per request, and the rate limit is a flat 20 requests per second on every plan with no 15-minute windows. Authentication is a single header, no OAuth handshake:

bash
curl -H "ApiKey: YOUR_KEY" "https://api.sorsa.io/v3/info?username=elonmusk"

If you want the reasoning behind why the official API became so costly to begin with, our explainer on why X's API pricing climbed so steeply covers the history and the business logic.

A small analytics team of around eight people we worked with started the way most do, assuming a free tier still existed. The official free access let them authenticate, but every tweet search returned nothing usable, and a third-party trial credit they tried next ran out before the prototype was finished. After switching to a flat read plan, they brought their data costs down by roughly 30 to 50 times versus per-resource official pricing for the same read volume, and stopped budgeting around credit balances entirely. The pattern holds for any read-heavy workload: the savings come from flat per-request billing and from author profiles being included rather than billed separately.

Getting started without paying to test

You do not need a paid plan to see whether the data fits your project. Run real queries for free in the playground, then, when you are ready to pull data in code, Sorsa's request-based plans start at $49 a month for 10,000 requests with a flat 20 requests per second, a single API key, and no approval queue. If you also need the official key for write actions, our step-by-step guide on getting an X API key walks through that path.

Frequently asked questions

Is the Twitter (X) API free in 2026?

No. The official X API has no free tier for new developers in 2026. New accounts start on pay-per-use, where you buy credits before making any call and pay per resource: about $0.005 per post read and $0.010 per profile, with no free read allowance and no monthly minimum. Verified public-utility accounts remain the only exception.

Is there a free way to get X data without the official API?

You can test endpoints for free in a browser. Sorsa API runs a free playground where you can run a profile lookup, a tweet search, or a follower pull through a UI with no API key and no signup. Pulling that data programmatically through the API itself requires a paid key, starting at $49 a month for 10,000 requests.

Is web scraping a free alternative to the X API?

Only on paper. Browser scraping with Playwright or Puppeteer is free in code but needs residential proxies and gets IP-blocked within hours behind X's login wall. Open-source libraries like snscrape and twint are broken or archived, while Twikit and TweeterPy still work intermittently but break on every X frontend change and violate X's terms of service.

Is the Twitter API free for academic research?

No. X closed the free Academic Research track to new applicants in 2023 and removed the academic API endpoints in June 2023. A narrow access path tied to the EU Digital Services Act exists for systemic-risk research, but X has approved very few requests. Most academic projects now pay pay-per-use rates or use a third-party data provider.

What is the cheapest way to read X data in 2026?

For read-heavy work above roughly 10,000 reads a month, a managed read-only API with flat per-request billing is the cheapest reliable option. Sorsa plans start at $49 a month for 10,000 requests, bill one request per call regardless of how much data it returns, and include the author profile in every tweet response, which the official API charges for separately.

Does the free X API let you search tweets?

No. Tweet search has never been part of X's free access, which is write-oriented. Under the 2026 pay-per-use model there is no free search quota either: every search request that returns data is billed per resource. To run tweet search without paying the official per-resource rate, developers use a third-party API or a managed data provider.


Reviewed by Keksich, founder of Sorsa, marketer and X API researcher.

This guide draws on Sorsa's day-to-day work operating a read-only X data API, cross-checked against X's own developer materials. Pricing and access facts were verified on June 13, 2026 against X's pay-per-use pricing documentation and the X Developers pay-per-use launch announcement (both linked above), and the status of open-source scrapers was checked against their current public repositories. The April 20, 2026 write and engagement price changes are reflected throughout.