Weir vs TwitterAPI.io (2026): Price, Coverage and When to Choose Each

Choose TwitterAPI.io if you need write actions (posting, liking, following), real-time streams, high request rates, or cheap bulk follower data. On the pay-as-you-go rate it is also cheaper per tweet than Weir's three smaller credit packs. Choose Weir if you want public X and Reddit data behind one key, free credits every month, and an MCP server that signs in with OAuth from Claude or ChatGPT.

Disclosure: Weir is our product. Everything about TwitterAPI.io below comes from its own pricing, docs and homepage, checked on October 19, 2026 and linked inline. Prices change, so check them before you commit.

Weir vs TwitterAPI.io at a glance

Sources: TwitterAPI.io pricing, pricing details, subscriptions, QPS limits, homepage; Weir pricing.

Price per tweet: the honest arithmetic

TwitterAPI.io charges 15 credits per tweet, which is $0.15 per 1,000 tweets on pay-as-you-go. Every call has a 15-credit minimum, so an empty search still costs $0.00015.

Weir charges 1 credit per X post plus 1 credit per successful call. X search returns about 20 posts per page, so 1,000 posts take about 50 calls: 1,050 credits. What that costs depends on the pack you bought:

So at small volumes TwitterAPI.io is cheaper per tweet. Weir's two largest packs come in under its pay-as-you-go rate. TwitterAPI.io's subscriptions push its rate lower again: its pricing details put the Business plan at about $0.00008 per tweet, which beats every Weir pack. That plan is $1,499 a month.

Follower data is not close. TwitterAPI.io charges 1 credit per follower when you take pages of 200, which is $0.01 per 1,000. Weir charges 1 credit per account, which is $0.10 to $0.20 per 1,000. If follower graphs are your main workload, TwitterAPI.io is 10 to 20 times cheaper.

Where TwitterAPI.io wins

• Writes. It can post, reply, like, retweet, follow and send DMs, at 200 credits ($0.002) per write call according to its pricing details. Weir can't write at all.
• Real-time delivery. Webhook filter rules and WebSocket streams with "sub-second delivery" (homepage). Weir's monitors run on a schedule, at most hourly.
• Throughput. Any account that has paid once gets 20 requests per second, and the Business plan gets 500 (QPS limits). Weir's top tier is 600 requests per minute, and a search counts as 2.
• Bulk followers and profiles. Followers at $0.01 per 1,000, and batch profile lookups of 100 or more at 1 credit each.
• Endpoint breadth on X. About 76 endpoints against Weir's 25 for X.

Where Weir wins

• Reddit in the same API. Search, communities, comment trees and user histories, with the same key and the same credit balance. TwitterAPI.io covers X only.
• Free credits every month. 5,000 credits each month, enough for about 4,700 posts from search. TwitterAPI.io gives $1 once, and it expires after 31 days. Accounts that have never paid are also limited to one request every five seconds.
• Large packs. At the $200 and $1,000 packs, Weir is cheaper per tweet than TwitterAPI.io's pay-as-you-go rate, and purchased credits never expire.
• MCP for chat apps. Weir's MCP server signs in with OAuth, so it works as a connector in Claude and ChatGPT without pasting a key (setup).
• Failed calls are free. A call that fails or is refused costs nothing, and every response states its charge in the x-credits-charged header.
• Monitors. A saved query runs on a schedule and reports only new items, with signed webhooks, so you don't have to write the deduplication yourself (docs).

Worked cost example

A social listening tool reads 100,000 tweets a month from keyword searches, and once a quarter pulls the 200,000 followers of a brand account.

Tweets, monthly:

• TwitterAPI.io: 100,000 x 15 credits = 1,500,000 credits = $15.00.
• Weir: 5,000 calls + 100,000 posts = 105,000 credits. Take off the 5,000 free monthly credits and 100,000 are paid. That's $20.00 at the $5 pack's rate, $14.71 at the $50 pack's and $12.50 at the $200 pack's. A year of this is 1.2 million paid credits, which one $200 pack covers.

Followers, quarterly:

• TwitterAPI.io: 200,000 x 1 credit at 200 per page = 200,000 credits = $2.00.
• Weir: X serves about 70 followers per page, so about 2,858 calls. That's 2,858 + 200,000 + 2 (one profile lookup to resolve the account) = 202,860 credits, or $20.29 to $40.57.

If the follower pull is a big part of your workload, the follower bill decides it in TwitterAPI.io's favour. If you mostly search and also need Reddit, the two are close on X, and Weir saves you running a second provider for Reddit.

Migrating from TwitterAPI.io to Weir

The data model is similar, because both return X's camelCase field names. The differences are auth, the request shape and pagination.

TwitterAPI.io's advanced search is a GET with the query in the URL and the key in X-API-Key (docs):

curl "https://api.twitterapi.io/twitter/tweet/advanced_search?query=from%3AXDevelopers%20api&queryType=Latest" \
  -H "X-API-Key: $TWITTERAPI_IO_KEY"

Weir's search is a POST with a JSON body and a bearer key. X search operators still work inside query, or you can use the structured fields:

curl https://api.weirapp.io/v1/x/search \
  -H "Authorization: Bearer $WEIR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "api", "fromUsers": ["XDevelopers"], "sort": "latest", "limit": 20}'

What changes in your code:

likeCount, retweetCount, replyCount, quoteCount, bookmarkCount, viewCount, conversationId and inReplyToId keep the same names. Post ids are strings in both. Counts in Weir can be null when X didn't report them, so don't treat a missing count as zero (response shapes).

If you use TwitterAPI.io for writes, keep it for those. Weir has no write endpoints, so a common setup is reads on one provider and writes on another.

FAQ

Is TwitterAPI.io cheaper than Weir?

Per tweet, yes, unless you buy Weir's $200 or $1,000 packs. As of October 2026 TwitterAPI.io is $0.15 per 1,000 tweets on pay-as-you-go. Weir works out to $0.105 to $0.21 per 1,000 from search, depending on the pack. For followers TwitterAPI.io is much cheaper at every size.

Can Weir post tweets like TwitterAPI.io?

No. Weir is read-only. For posting, liking or DMs use TwitterAPI.io or the official X API.

Does TwitterAPI.io cover Reddit?

Its homepage and docs describe X only. Weir covers X and Reddit with one key.

Which has the better free tier?

It depends on how long you need it. TwitterAPI.io's $1 is 100,000 credits, about 6,600 tweets, once, and it expires after 31 days. Weir's 5,000 credits come back every month, which is about 4,700 posts from search.

Do both have MCP servers?

Yes. TwitterAPI.io advertises a hosted MCP server. Weir's is at https://api.weirapp.io/mcp, with OAuth sign-in for Claude, ChatGPT and coding agents. See Reddit and X MCP server for Claude and ChatGPT.

A note on terms

Both are third-party services reading public X data. Neither is X, and each has its own terms. How you use the data is still governed by the law and by X's rules. This isn't legal advice.

Trying Weir

Sign up to get the 5,000 free monthly credits, or start from the quickstart. For the wider field, see Best Twitter API alternatives and pricing.

Sources

• TwitterAPI.io pricing: https://twitterapi.io/pricing
• TwitterAPI.io pricing details: https://twitterapi.io/pricing/details
• TwitterAPI.io subscriptions: https://twitterapi.io/subscribe
• TwitterAPI.io QPS limits: https://twitterapi.io/qps-limits
• TwitterAPI.io homepage: https://twitterapi.io/
• TwitterAPI.io advanced search docs: https://docs.twitterapi.io/api-reference/endpoint/tweet_advanced_search
• Weir pricing: https://weirapp.io/pricing
• Weir response shapes: https://docs.weirapp.io/response-shapes
• Weir monitors: https://docs.weirapp.io/monitors
• Weir MCP for chat apps: https://docs.weirapp.io/mcp-chat-apps