X API Pricing: Official vs Public Data

"Twitter API pricing" and "X API pricing" are the same question with two brand names. Teams search it when a monitoring cron, creator scorecard, or research agent needs public profiles and posts. Then they land in X's developer console, which prices first-party access for a bigger product than "pull this handle."

Use the official X API when you need posting, OAuth-on-behalf-of, elevated first-party products, or a contract that must say "X." Use Social Fetch when you need public profiles, tweets, replies, search, communities, or transcripts without an X developer app, with prepaid credits, the same envelope as TikTok and Instagram, and charges only on completed lookups. Confirm live X rates in the developer console, because packaging has moved more than once.

How I compared the options

I apply the same criteria to every option and record them in the table below: how you get access, how you are charged, what X data you can reach, and who the option fits. X's figures come from X's pricing docs, checked October 2026, and Social Fetch's come from our pricing page as of October 2026. I do not quote figures for the other vendors, because their plans change and each publishes its own page.

1. Social Fetch

Best for: monitoring crons, creator scorecards, and research agents that need public X profiles, tweets, replies, and search beside other social platforms.

Strengths: Social Fetch exposes public X data under /v1/twitter/...: profile by handle, profile tweets, tweet detail, replies, tweet transcript, keyword search, hashtag search, community detail, and community tweets. Responses use the same { data, meta } envelope and x-api-key as the rest of the catalog. One key covers 23 platforms and 232 documented operations, there is an MCP server for AI agents, and failed lookups are free. Pay-as-you-go credits never expire, and there is no required subscription.

Limitations: you do not get posting, DMs, or X's elevated first-party products, because those belong on X's API. Social Fetch covers 23 platforms, not forty. A completed not_found still bills because the lookup finished.

Pricing: pay-as-you-go starts at $14 for 1,000 credits, and new accounts get 100 free credits with no card. Larger volume runs from $1.35 per 1,000 credits on the Scale annual plan, or $1.64 per 1,000 on the Scale pack, as of October 2026 on pricing. Every Twitter route costs 1 credit per completed lookup, including keyword search, hashtag search, profile tweet pages, and reply pages. Trust meta.creditsCharged on every response. Validation errors and infrastructure failures (lookup_failed, 503 temporarily_unavailable) do not debit.

Full route list: X (Twitter) platform hub. Search filters and pagination: Twitter search API.

2. X API

Best for: posting, replies, likes, follows, member OAuth, and products that need a contract that says "X."

Strengths: it is the first-party source, and the only route to write paths and elevated products. Billing is pay-per-use with no subscriptions, contracts, or minimum spend, and no Basic or Pro tiers.

Limitations: reads bill per resource returned rather than per HTTP call, so a keyword search that returns 20 posts can bill as 20 post reads. Pay-per-use is capped at 3 million post reads per monthly billing cycle, and above that X routes you to an Enterprise plan. Packaging moves, and legacy plan names still float around in old posts and RFPs.

Pricing: the per-resource rates below come from X's pricing docs, checked October 2026.

• Post read: $0.005 per post.

• User read: $0.010 per user.

• Followers and following read: $0.010 per resource.

• Like read: $0.001 per like.

• Owned reads (your own account's data): $0.001 per resource.

• Create a post: $0.015 per request.

• Create a post containing a URL: $0.200 per request.

A search returning 20 posts is therefore $0.10 on X's meter. On Social Fetch the same search page is 1 credit per completed lookup, which is $0.00135 to $0.014 depending on plan or pack. Side-by-side on capabilities, limits, and terms: Social Fetch vs the X API.

3. EnsembleData

Best for: teams that want steady daily sync volume from one provider that includes X among several platforms.

Strengths: a sync REST API with plan-based pricing, which suits predictable workloads.

Limitations: daily unit caps reset on a schedule, so spiky research sprints can hit the ceiling. Side-by-side: Social Fetch vs EnsembleData.

Pricing: monthly plans, so check the vendor's pricing page for current tiers.

4. SociaVault

Best for: simple pay-as-you-go lookups where a smaller catalog is enough.

Strengths: prepaid credits with no subscription, which is the same basic billing shape as Social Fetch.

Limitations: the catalog is smaller, so check that the X routes you need exist before you commit. Side-by-side: Social Fetch vs SociaVault.

Pricing: prepaid credit packs, so check the vendor's pricing page for current pack sizes.

5. Apify

Best for: custom fields and scheduled scrapes that no managed REST route exposes.

Strengths: a large Actor marketplace, plus scheduling and dataset export built into the platform.

Limitations: you start a run and poll for results, schemas differ by Actor author, and a sync request handler fits poorly. Side-by-side: Social Fetch vs Apify.

Pricing: billing mixes a platform subscription, compute, and per-event Actor fees, so model the Actor you will actually run.

6. RapidAPI listings

Best for: weekend discovery of a niche X endpoint before you commit to a contract.

Strengths: many publishers behind one billing account, which makes trying several listings quick.

Limitations: there is no shared schema, and pagination, freshness, and support vary by publisher, so it is a weak base for production monitoring. See vs RapidAPI.

Pricing: set per listing by each publisher.

What "Twitter API pricing" usually means

Three different products get collapsed into one phrase.

1. Official X developer products. Apps, scopes, rate limits, and whatever credit model X is selling this quarter. Source of truth: developer.x.com and X's pricing docs.

2. Public enrichment APIs. Third-party REST for publicly visible profiles and posts, with no X developer app. You pay the vendor's credit or unit meter.

3. Scrapers and Actors. Run-based or browser automation, which suits custom fields but carries a different ops and compliance model than sync REST.

Mixing the first two is how budgets blow up. Official access is priced for X's product surface, meaning writes and elevated reads, while public enrichment is priced for looking up a handle and returning JSON. If someone on your team still asks whether X has an API at all, see Does Twitter (X) have an API?.

Why the official meter is aimed at a different buyer

A few structural reasons show up in almost every evaluation, whatever X's page says today.

• Official products assume apps, review, and scopes, which is correct when you post as users and dead weight when you only enrich public handles.

• X replaced its free allowance and fixed monthly Basic and Pro tiers with pay-per-use billing, so treat third-party screenshots of old monthly plans as history.

• Brand monitors and research crons care about keyword search and profile reads, and per-resource billing is where official math hurts first.

• Adding an X developer stack beside a vendor you already use for TikTok and Instagram means a second auth model, a second error shape, and a second invoice.

That is a meter mismatch rather than a quality judgment. If your ticket says "Twitter API" but the acceptance criteria are "confirm the handle exists and store follower count," you are buying a profile GET and not write scopes. Vendor shortlist: Best Twitter/X data APIs in 2026.

Rough cost shape on Social Fetch

Do not paste an old third-party X dollar table into your spreadsheet. Use the X rates above, confirm them in X's pricing docs before you commit a budget, and model Social Fetch from the pack math on pricing.

• Prototype and QA: tens to hundreds of credits, covered by the free 100 credits and then the $14 Starter pack of 1,000 credits.

• Light monitoring: roughly 1,000 to 5,000 credits, on Starter or the next pack.

• Steady enrichment: tens of thousands of credits, on Growth or Scale packs at $1.64 per 1,000 on the Scale pack, or down to $1.35 per 1,000 on the Scale annual plan.

Search and paginated tweet or reply pages cost the same 1 credit per page as a profile GET, so model pages rather than posts. Empty result pages can still complete a lookup, so budget for that or cache known-good queries.

Final recommendation

• Choose the X API if you need to post, reply, like, or follow, need member OAuth, or procurement requires X-signed access and compliance products.

• Choose Social Fetch if the job is public enrichment, because lookups are priced per completed page, credits never expire, and failed lookups are free.

• Choose Apify if you need custom fields or scheduled dumps and can live with polling a run.

For the write paths only X can provide, Social Fetch is a complement for public enrichment elsewhere in the stack and not a substitute.

Frequently asked questions