Compare / X API · Prices read on
Feeds vs the X API for new posts
The X API is the official way to read X. It is pay-per-use now: you buy credits and each read is deducted. Feeds sits on top of the job of following accounts: it checks each one at its own pace and delivers each new post once.
Side by side
| X API | Feeds | |
|---|---|---|
| Unit you pay for | Each post or user a call returns | Each check and each new post |
| Price | $0.005 a post read, $0.010 a user read | 1 credit a check, 1 credit a post, about $0.001 a credit |
| Monthly limit | 3 million post reads, then Enterprise | Your plan’s credits plus top-ups |
| Polling and state | You build the scheduler and store the last post | Built in, with slower checks while an account is quiet |
| Delivery | You build it | A signed webhook per post, the REST API, or RSS |
| Search, writing posts, other endpoints | Yes | No |
| LinkedIn in the same format | No | Yes |
What it costs to follow 10 accounts
Each account checked every hour, about 5 posts a day:
- On the X API, about 1,500 new posts a month × $0.005 = about $7.50 a month, if each call returns only new posts.
- On Feeds, the same 10 accounts use 8,700 credits a month at most. That fits the $19 Starter plan.
The X API is the cheaper choice if you already run workers and queues. Feeds saves you the scheduler, the state per account, the deduplication, and the delivery. Read the full math in X API pricing in 2026.
Which one to pick
- Pick the X API if you follow only X, you need search or write endpoints, or you read millions of posts.
- Pick Feeds if you want new posts in your app today, you also follow LinkedIn, or you want a hard cap per account.
Rates are from X’s pricing page, read on 2026-11-12. Check it before you decide.
X is a trademark of X Corp. Feeds is not affiliated with X Corp.
Start with 1,000 free credits, no card.