RapidAPI scraper

What RapidAPI is now

RapidAPI started as an API marketplace. At its peak it counted 4 million users and some 40,000 APIs. Then it shrank. Nokia acquired the technology assets on November 13, 2024 (Nokia press release). TechCrunch reported the active user count was in the thousands and APIs in the hundreds at the time of the deal (TechCrunch). Before that, it was once valued at $1 billion (same article).

RapidAPI’s own FAQ still says “over three million developers” (docs.rapidapi.com). The search result counts on the site include fuzzy matches and inactive listings and should not be read as a count of live APIs.

The Terms of Use (updated May 13, 2026, operated by “Nokia of America Corporation, dba Rapid”) say the API terms are “solely between each such API Consumer and such API Provider, and not with Rapid” (rapidapi.com terms). “NO REFUNDS WILL BE ISSUED” (same terms).

The marketplace fee became a flat 25% on November 15th, 2025 (payouts docs): the provider receives the rest minus PayPal payout fees.

What “unofficial API” means on RapidAPI

A RapidAPI scraper listing is a third party’s endpoint. You send requests to RapidAPI’s proxy, it routes them to the provider’s server, and the provider scrapes the target site. The provider handles authentication, proxies and anti-bot evasion on their side.

The listings say this themselves. twitter-api45, the top Twitter listing by subscriptions (30,478), describes itself as “Unofficial cheap Twitter / X API.” The listing carries 42 billing plans, including private custom ones. The provider’s contact is a Telegram handle.

You get one X-RapidAPI-Key per app, shared across every API you subscribe to (keys docs). The convenience is real: one key, one billing dashboard, test endpoints in the browser. The risk is that you depend on an anonymous provider with no SLA, behind a marketplace with no refunds.

Subscriber counts: RapidAPI vs Apify

Both marketplaces publish usage numbers, but the units differ (RapidAPI: subscriptions; Apify: users). By portal, the top listing or actor for each:

Portal	RapidAPI top (subs)	Apify top (users)
Amazon	45,454	26,583
X/Twitter	30,478	110,690

On X, Apify’s top actor is far ahead. On Amazon it’s the other way round: RapidAPI’s top listing has more subscriptions than Apify’s top actor has users. Subscriptions and users aren’t the same unit, so read this as rough scale, not a ranking. Either way, RapidAPI is not the ghost town its Google presence suggests.

How to vet a RapidAPI listing

Popularity scores won’t help you choose. Nearly every live listing sits at the top of the scale, so the score tells you a listing isn’t dead, and not much more.

What to check instead:

Success rate. The listing page shows it. Socialgrep: 0% success, status ACTIVE, still selling a $100/mo plan. logicbuilder’s Amazon API: also status ACTIVE, success rate at zero, still selling.

Last updated date. Socialgrep was last updated on 2024-07-03. A listing that hasn’t changed in a year or more, on a site that changes often, is a warning sign.

Test the free tier first. Many listings have a free plan. Send a real request before subscribing. NO REFUNDS WILL BE ISSUED.

Read the “About” text. If it says “Unofficial” or gives a Telegram contact, the provider is an individual or small shop. That is not inherently bad, but it means no SLA, no guaranteed uptime, and no one to call if it stops.

Check the endpoint list. Some listings wrap a single endpoint. Others cover dozens. The listing page shows them.

The dead-but-still-selling problem

RapidAPI’s terms say it “may” delist APIs at its “sole discretion” (rapidapi.com terms). In practice, dead APIs stay listed and sellable.

Socialgrep (by Lexyr): status ACTIVE, 0% success, still offers a $100/mo plan. logicbuilder’s Amazon API: same pattern. Both show “ACTIVE” status. Both have zero percent success. Both still accept subscriptions. And NO REFUNDS WILL BE ISSUED.

Legal: what the record shows

This is not legal advice. These are facts from court records and regulator guidance, each with its source. They apply to scraping generally, not only to RapidAPI.

X’s Terms of Service (effective Oct 9, 2026): “crawling or scraping the Services in any form, for any purpose without our prior written consent is expressly prohibited” (x.com/en/tos). Liquidated damages: “$15,000 USD per 1,000,000 posts” accessed in any 24-hour period. Added in the ToS effective November 15, 2024 (Knight First Amendment Institute).

X Corp. v. Bright Data (N.D. Cal., May 9, 2024): Judge Alsup dismissed X’s claims, in part as preempted by the Copyright Act: “risks the possible creation of information monopolies that would disserve the public interest” (Courthouse News).

Meta v. Bright Data (N.D. Cal.): summary judgment for Bright Data on “logged off” scraping (Quinn Emanuel). Meta has dropped its lawsuit (TechCrunch, via SERP snippet).

hiQ v. LinkedIn (December 2022): $500,000 consent judgment against hiQ, plus a permanent injunction (reported by Proskauer, via SERP snippet).

GDPR (EU): “Met scraping worden bijna altijd persoonsgegevens verzameld” (scraping almost always collects personal data), Dutch DPA, 02 april 2025 (autoriteitpersoonsgegevens.nl).

The r/webdev thread “Aren’t all Rapid API’s all mostly Illegal?” asks the right question. The answer is: it depends on the site, the data, the jurisdiction, and whether the provider or the consumer carries the legal risk. RapidAPI’s terms put it solely between the buyer and the provider.

Where FATSEARCH fits

FATSEARCH is not a scraping API or a RapidAPI alternative. It reads one public page at a time for an AI agent, through the user’s own provider key. If your agent needs to read a single page from a site as part of answering a question, FATSEARCH does that without a scraping subscription.

For bulk data, follower lists or historical archives, the scraping routes in our how to scrape Twitter guide are the right tool. For what FATSEARCH returns on hard pages vs other readers: web scraping MCP. Setup: web search MCP for Claude Code. The benchmarks doc shows where FATSEARCH loses on social pages too. And why Claude Code’s web fetch gets refused covers what happens when a site blocks the built-in fetch.