X API vs scraping in 2026: costs and tradeoffs

November 8, 2026

If you need X (Twitter) data, you choose between three paths: the official API, building your own scraper, or buying from a third-party data API. The sticker price is only part of the cost. This post puts numbers on the official option and lists the hidden costs of the others.

The official X API in 2026

X now sells API access pay-per-use, with no subscription or minimum spend. You buy credits and each request deducts from them. X

Action	Price
Read a post	$0.005
Read a user	$0.010
Read followers or following	$0.010 each
Trends	$0.010
Create a post	$0.015 ($0.200 with a URL)
Your own data ("owned reads")	$0.001

Repeat reads of the same resource within a UTC day are deduplicated, which X calls a soft guarantee. Pay-per-use is capped at 3 million post reads per billing cycle; above that, Enterprise. You can set a spending limit. source

What common jobs cost on the official API

Job	Volume	Official API cost
Enrich a lead list	10,000 profiles	$100
Monitor a brand	50,000 posts a month	$250 a month
Research dataset	1,000,000 posts	$5,000
Follower export	100,000 followers	$1,000

The real cost of building your own scraper

Terms. X's terms say crawling or scraping "in any form, for any purpose without our prior written consent is expressly prohibited". X terms
Liquidated damages. The same terms say that if you breach them, X can claim $15,000 per 1,000,000 posts requested, viewed or accessed in any 24-hour period above that volume. source
Venue. Disputes go to federal or state courts in Wichita County or Tarrant County, Texas, except for users in the EU, EFTA states and the UK. source
Logins. Open-source tools such as twscrape say they require authorized X accounts. source Those accounts can be suspended.
Maintenance. Internal endpoints change without notice. Budget engineer time every month.

Read our separate post on the legal cases before you decide. This is not legal advice.

The middle path: third-party data APIs

Third-party APIs sell read access to public X data per request. They are much cheaper per item than the official API for reads, and you do not run any scraping yourself. The tradeoffs: they are read-only, they depend on the vendor's own access, and terms questions shift to the vendor rather than disappear.

	X API	Own scraper	Third-party API
Read price	$5 per 1,000 posts	Engineering time	From $0.15 per 1,000 tweets source
Write (post, DM)	Yes	Against terms	No
Full archive	Yes	Hard	Varies
Contract with X	Yes	No	No
Maintenance	Low	High	Low

Questions to ask any third-party vendor

Are failed, empty and not-found results billed?
Do prepaid credits expire, and when?
What is the rate limit, and how is it raised?
How fresh is the data: live on request, or from a database refreshed weekly?
Which fields are missing compared with the official API?
What happens to your integration if the vendor loses access?

A decision checklist

Do you need to post, reply, DM or act for users? Official API.
Do you need a direct agreement with X for compliance or procurement? Official API.
Read-only, public data, cost-sensitive? Price a third-party API against the official one at your volume.
Building your own scraper? Count the terms, the damages clause and the maintenance first.

Doing it with ScrapeIO

ScrapeIO is a read-only API for public data and cannot post or act as a user. X calls such as the X profile API and the X user posts API cost 1 credit, which is $0.99 to $1.88 per 1,000 calls; failed and not-found calls are free. See the X API comparison for a side-by-side.

Sources

Checked on 8 November 2026 from each vendor's own pages. Prices and limits change; follow the links before you decide.

100 free credits, no card. Credits never expire.

Get API key