Geonode logo

Unlimited Twitter scraper for AI agents.

Posts, profiles, full threads, replies, search results and trending topics on X. Unlimited requests for one flat bill from $50/mo, no credits, and a blocked request is free.

Start 48-hour free trial

No card. Unlimited pages. 5 threads. Failed requests $0

Unlimited web scraper
01

Images

02

Title

  • Title
  • Condition
03

Price & bidding

  • Price
  • Bids
  • Time left
  • Watchers
04

Seller

  • Seller rating
  • Sold listings
05

Specifics & shipping

  • Item specifics
  • Shipping
  • Item location

JavaScript rendered, parsed to JSON or Markdown, and a fetch that fails after three retries is never billed

Call it on Twitter

curl -X POST "https://scraper.geonode.io/v1/extract" \
  -H "X-Api-Key: $GEONODE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "url": "https://x.com/elonmusk/status/1812258574049157405",
  "formats": [
    "json",
    "markdown"
  ],
  "render_js": true,
  "proxy": {
    "country": "US"
  }
}'

You came for an Twitter scraper. The key opens everything.

100% first-pass success

you’re here

Post: Post text, Author handle, Timestamp, Media attachments, Quoted post, Edit history flag

Engagement bar: Reply count, Repost count, Like count, Bookmark count, View count

Thread and replies: Self-thread continuation, Top replies, Reply authors, Community note, Reply restriction

Profile header: Display name, Bio, Location, Join date, Followers / following, Verification badge type

Search and trends: Top vs Latest tab, Result posts, Trend name, Trend post count, Trend category

One subscription, from $50 a month flat. Everything after the first line adds $0

The hard part is getting in. That's our part.

  • $50/moflat, priced by concurrency, not per request

  • 0credits, meters or per-page charges

  • $0for any Twitter request that still fails after 3 retries

  • 48 hfree trial on your own Twitter URLs

  • Cloudflare98%

  • Akamai97%

  • Imperva Incapsula97%

  • DataDome96%

  • PerimeterX / HUMAN95%

  • reCAPTCHA v395%

  • Kasada94%

  • hCaptcha93%

First-pass success by anti-bot vendor, measured by us over 30 days, so of course it flatters us. The 48-hour trial exists so you can count against your own URLs. Full benchmark

What unlimited changes for Twitter data

  • Sold-comps pricing

    Completed listings are the real price of anything. Pull them at scale and price with evidence.

  • Arbitrage sourcing

    Sweep categories for mispriced inventory continuously instead of when the credit budget allows

  • Demand research

    Bids, watchers and sell-through, across a whole category, on one flat bill

  • Collection tracking

    Every listing of the thing you care about, the moment it appears

Cheap is supposed to be the trade-off

  • Michael T.

    Switched from Bright Data. Same quality, fraction of the cost. Their wholesale model actually makes sense.

  • Kristina Halvorson

    Finally a proxy provider that actually feels built for developers

  • Edgar Weissnat

    We run multiple large-scale data collection pipelines across several regions, and proxy reliability has always been one of the biggest bottlenecks. After switching to Geonode we noticed two immediate improvements: connection stability and predictable pricing. Previously we had to constantly optimize traffic to avoid massive proxy bills. With Geonode’s wholesale pricing model we can focus on building products instead of worrying about proxy usage. Integration with our Python stack and Playwright automation was straightforward and took less than a day.

  • Gladys Paucek

    Best proxy infrastructure I've used. The MCP integration with our AI agents was seamless.

  • Gladys Paucek

    Finally something that doesn’t feel like enterprise sales software.

Pick your thread count. That's the only decision.

Nothing is metered. Plans price threads (how many requests run at once), and pages stay unlimited on every one. An Twitter page that needs an anti-bot bypass costs exactly what a plain page costs

Roughly what each plan clears in a month, by endpoint

Starter

2 threads

$50 /mo

~470K
~280K
~1.1M
~610K
~120K
~400K
Start free

Growth

5 threads

$100 /mo

Popular
~1.2M
~700K
~2.8M
~1.5M
~300K
~1M
Start free

Scale

25 threads

$400 /mo

~5.9M
~3.5M
~13.8M
~7.6M
~1.5M
~5M
Start free

Pro

100 threads

$1,250 /mo

~23.5M
~14M
~55M
~30M
~5.9M
~20M
Start free

Max

250 threads

$2,500 /mo

~59M
~35M
~137M
~76M
~15M
~50M
Start free

The 48-hour trial runs at five threads, no card. Custom terms past 250 threads.

Yeah, but...

We do not yet publish a benchmark number for x.com. The domain is a special case: X moved almost everything behind a login wall in 2023 and the guest-token path it leaves open is deliberately narrow, so a success rate measured on one page type would mislead you about another. What we can say is that the Twitter scraper handles the token and transaction-ID dance for you, retries with a fresh session when X returns an empty response, and a request that still fails after three retries is never billed, on any plan.

Single posts with their media, quoted post and Community Note; the author's own thread continuation; the visible top replies; public profiles with bio, join date and follower counts; search results on both Top and Latest tabs; and the trending list per country. Twitter Spaces, DMs, lists and anything that needs a specific logged-in account are out of scope for the Twitter scraper, because a Twitter scraper that logs in with borrowed accounts gets those accounts banned within days. The twitter_post target also accepts legacy twitter.com URLs, since X still redirects them and the post IDs did not change with the rename.

Any Twitter scraper is bound by how X paginates: opaque cursors, not page numbers, and the depth it allows a non-logged-in session is far lower than what you see when signed in. For replies we follow the cursor until X stops returning new posts, which on a viral post means the ranked top replies rather than every one of fifty thousand. For search, the Latest tab goes back further than Top, and both stop sooner than the week or so you would get through the official API. If you need historical posts beyond that window, scraping Twitter by date range is not a reliable route and we will say so rather than sell it as one.

The rename from Twitter to X changed the domain and the terms of service wording but not the law. Public posts are public data, and US courts have repeatedly declined to treat collecting them as unauthorized access; X's own lawsuits against Twitter scraper operators have leaned on contract terms, which bind an account holder, not an anonymous visitor. Our Twitter scraper never logs in, never uses your credentials and never touches protected accounts, which keeps it on the public-data side of that line. Check your own jurisdiction and purpose before you store personal data pulled from profiles.

No request credits and no per-page meter. Plans are priced by concurrency, which is the number of requests in flight at once, from $50 a month. Run as many requests through that concurrency as you can, around the clock, for the same bill. A request that fails after three retries is not counted against anything.

Yes. Pass a country code and the request routes through a residential IP there, so marketplaces return local prices and currency, search engines return local results, and geo-restricted pages open. City and ASN targeting are available on the residential pool where a site is sensitive to it.

Typed JSON with the field table on this page, clean Markdown for feeding an LLM context window, or raw rendered HTML if you run your own parser. For pages without a dedicated parser you can pass a JSON schema and get AI-extracted fields back in that shape.

48 hours. Your worst Twitter URLs.

Five threads, no card, and the clock starts at your first API call. If it doesn’t earn the switch, don’t switch.

Start the trial