Scraping API PricesHome / Cost to scrape / X, formerly Twitter
Cost to scrape X, formerly Twitter at 10K, 100K, and 1M
Published X, formerly Twitter scraping rates, plan costs at three billable volumes, access facts, protections, and the official API option.
Access
Protections in the way
Terms
What you scrape moves the bill more than who you buy from. A target that forces JavaScript rendering or a residential exit multiplies the meter before any plan is chosen.
What each vendor charges for this target
| Product | Costs | Source |
|---|---|---|
| ScrapingDog | 5 credit | source |
Access fact, checked 2026-07-26: X’s Terms prohibit crawling or scraping the service without prior written consent except where a robots.txt file expressly permits it (Source).
Cost to scrape X, formerly Twitter at 10K, 100K, and 1M table
| Route | 10K | 100K | 1M | Billing rule and source | Checked |
|---|---|---|---|---|---|
| Bright Data Web Unlocker and Web Scraper API: X Scraper API | Not published | Not published | Not published | Target endpoint is documented, but no target-specific public rate is in the record | 2026-07-26 |
| X API | $50 Post / $100 User | $500 Post / $1,000 User | $5,000 Post / $10,000 User | Pay-per-use pricing includes $0.005 per Post read and $0.010 per User read, subject to the published pricing table. | 2026-07-26 |
The comparison uses 10,000, 100,000, and 1,000,000 billable target calls or delivered results per month, calculated on 2026-07-26. It does not claim those calls all become useful rows. Credit, request, result, and search meters are passed through the dataset quote model, which selects the least expensive published self-service offer that covers each volume. A starting USD rate is shown as a lower bound because an unpublished minimum, tier, or contract can raise the invoice. Retries, pagination, duplicate outputs, taxes, and data licensing are outside these figures.
No public target price was found
The dataset contains no published surcharge or target-specific unit rate for X, formerly Twitter. A vendor may document a dedicated endpoint without publishing what that endpoint costs at these volumes. Those rows remain “Not published” rather than borrowing a generic request price, because a generic price does not prove target support, residential routing, rendering, parser coverage, or the target-specific contract. The unknown is the answer until a first-party rate is published.
Rendering and access change the job
This record classifies X, formerly Twitter as very-hard and records rate limiting, CAPTCHA, bot detection and fingerprinting, a login wall, IP reputation checks, dynamic rendering, TLS fingerprinting. JavaScript rendering is required in the recorded profile, so a plain HTML request is not the same workload. Residential routing is recorded as needed, but no generic proxy multiplier is silently added: the table applies only a vendor’s explicit target meter.
Public profiles, posts, comments, engagement, and authenticated views are different jobs, and login state can change both access and output.
The official route is a separate product decision
X API is recorded as available. Requires an approved developer account and project; product access and caps depend on the purchased tier. Pay-per-use pricing includes $0.005 per Post read and $0.010 per User read, subject to the published pricing table. X API directly prices supported Post and User reads, but the API schema and the rendered site are not field-for-field equivalents. Source and access status checked 2026-07-26.
Endpoint evidence and the remaining unknown
The dataset confirms 1 dedicated endpoint or template. This proves named target support in the cited product documentation. It does not prove that each endpoint has a public target-specific price.
- X Scraper API is documented, while its target-specific price remains unpublished in this record.
What volume means for X
One useful unit is one Post or User observation with a defined field list and collection time. Search or timeline endpoints discover Posts, while user lookup and conversation expansion are separate operations, so the workload must count those follow-up objects rather than treating a rendered timeline as one page (X API pagination, retrieved 2026-07-27).
X API endpoints paginate with tokens such as next_token and pagination_token; the supported maximum page size is endpoint-specific. Bright Data’s dedicated X product returns structured records, which changes the vendor planning unit from rendered pages to delivered Post or User records, but continuation and enrichment still depend on the chosen object (X API pagination, retrieved 2026-07-27; Bright Data X Scraper API, retrieved 2026-07-27).
The official X API can answer supported Post and User questions within the purchased access tier. It does not reproduce rendered timelines, advertising, recommendation treatment, or arbitrary authenticated views, so the API is not automatically the same product as page collection (X API pricing and access, retrieved 2026-07-27).
Evidence to check before buying
- X’s official API is pay-per-use and separately meters Post and User reads docs.x.com.
- Bright Data operates a purpose-built X scraper rather than treating it as a generic page brightdata.com.
- X’s terms specifically address crawling and scraping access x.com.
- Confirm the exact entity and output unit, whether a page, search, result, record, or API object. Then multiply by pagination and refresh frequency before selecting a plan.
- Keep public and authenticated collection separate. The recorded login wall means credentials can change both the permitted route and the returned fields.