WEIR

X API Expansions Billing From 22 Nov 2026: What It Costs

X API expansions billing starts 22 November 2026. See what author_id and media expansions add per call, a worked $1.30 example, and how to cut the bill.


Published · Updated · 7 min read · 阅读中文版 · 日本語で読む

Cover image: The expansion bill

X API expansions billing starts on 22 November 2026: every object in includes is billed at the normal pay-per-use rate.

A post that brings back a new author then costs $0.015, not $0.005.

This is for developers on X's pay-per-use API whose code sets expansions=. You get the new rates, what common calls cost, how to cut it, and a cheaper route. We run Weir, an X (Twitter) data API, and say so where it matters.

This call asks for authors and media (not run by us, as we have no X key; it follows X's docs):

curl "https://api.x.com/2/tweets/search/recent?query=from:NASA&max_results=100&expansions=author_id,attachments.media_keys" \
  -H "Authorization: Bearer $TOKEN"
$0.50100 posts, before and after
$1.30the same call with authors and media
$0.001per expansion object on your own posts

What changes with X API expansions billing on 22 November 2026?

The change log entry X has prepared for 22 November 2026 reads "Expansion objects now count toward usage." It means the includes section of a response, not only data.

We read the source on 16 November 2026. It is X's docs repository, pull request 520, opened on 28 October 2026. Its banner says not to merge it until expansion billing is enabled in production, planned for 22 November 2026.

X also posted a notice on its developer forum, titled "[Inform] X API PPU - Expansions Update". It blocks automated readers with a 403, so we did not open it. We took every number from the pull request.

Here is the rate list in that pull request:

  • Post $0.005 and user $0.010 per object, unchanged.
  • Media, poll, place and topic $0.005 each. These are new read rates.
  • Four photos on one post are four media objects, billed four times.

What does the X API pay-per-use expansions bill look like for a real call?

Each object counts once, so the bill is a sum.

Before 22 November the same calls cost only the posts.

Call (all new objects) Before 22 Nov After 22 Nov
100 posts, no expansions $0.50 $0.50
100 posts + author_id, 60 authors $0.50 $1.10
Same + attachments.media_keys, 40 media $0.50 $1.30
100 of your own posts, 1 user, 30 media $0.10 $0.131

The arithmetic for row three is 100 × $0.005 + 60 × $0.010 + 40 × $0.005, which is $1.30. That is the worked example in X's pull request. Row two is $0.50 plus $0.60.

The last row uses Owned Reads, X's name for reading your own posts, mentions and liked posts with your own app. Expansion objects there bill at $0.001, so 131 objects cost $0.131. Reading other people's data through OAuth is not an Owned Read.

What do X's docs say today?

On 16 November 2026 the live pricing page (changed 13 November) lists Posts: Read at $0.005 and User: Read at $0.010 per resource. It has no Media, Poll or Place read rows and no expansions section yet.

The live expansions page has no billing note either. It says expansions let you "include related objects in a single API response."

So the new rules are not on X's public docs until the pull request merges. Treat the pull request and the forum notice as the plan, and check the Developer Console on 22 November. Our guide to X API pricing in 2026 has the full rate card.

How to cut the bill

Most of the extra cost is users.

A call with author_id adds up to one $0.010 user per post, so cut there first.

  • Drop expansions you never read. X's tip in the pull request: request only the expansions your app uses.
  • Skip author_id when you already know the author. On a from: search, every author is the same account.
  • Cache profiles for a day. A cached user costs nothing, and X's dedup does the same within one UTC day.
  • Watch the Developer Console. Compare a day's spend with the sums above.

To see what a response will cost, count its objects. This sketch is not run, because we have no X API key:

import json

def estimate(resp: dict) -> float:
    inc = resp.get("includes", {})
    cost = 0.005 * len(resp.get("data", []))
    cost += 0.010 * len(inc.get("users", []))
    for kind in ("media", "polls", "places", "tweets"):
        cost += 0.005 * len(inc.get(kind, []))
    return round(cost, 4)

print(estimate(json.load(open("response.json"))))

It ignores dedup, so it is an upper bound. Your free credit plan matters too: see X API free credits for the one-time $20 and the match.

Is there a cheaper route than X API expansions?

Weir is one. On Weir each post in a search result carries its author, and the author is not billed on top. A post costs 1 credit and a call costs 1 credit.

We ran this on 16 November 2026: search_x for posts from @NASA, limit 20. It returned 20 posts for 21 credits.

{
  "id": "2121280846183137564",
  "createdAt": "2026-11-13T16:35:39.000Z",
  "author": {
    "username": "NASA",
    "name": "NASA",
    "verified": true,
    "followersCount": 92250508
  },
  "likeCount": 5169,
  "media": [{ "type": "photo" }]
}

The response meta showed creditsCharged: 21. The media list came with the post too. Eleven of the 20 posts were reposts, and each carried its original's author, from seven other accounts.

Now 100 posts. That is 5 pages of 20, or 105 credits. At the $5 pack (25,000 credits) it is $0.021, and at the $20 pack (120,000 credits) it is $0.0175.

100 posts with authors, in dollars
X API after 22 Nov (60 authors, 40 media)$1.30
X API after 22 Nov (authors only)$1.10
X API 100 posts alone$0.50
Weir, $5 pack$0.021
Weir, $20 pack$0.0175

So the same 100 posts with authors cost about 60 times less on Weir than X's $1.30 example. Compare other options in our X API price index, or plug in your own numbers in the X API cost calculator.

Weir's first 5,000 credits each month are free, with no card. See our X API alternative page or pricing.

When not to use Weir

  • You post, reply or like. Weir is read-only. Only X's API writes.
  • You need your own account's private data. Bookmarks, DMs and analytics need your own X login. Weir reads public data only.
  • A contract or compliance rule names X. Weir is not licensed by X, so access can change. Check the terms that apply to you; this is not legal advice.
  • You need firehose volume. Millions of posts a day is a different tier, and a quote from X or an enterprise data vendor fits better.

FAQ

Will my X API bill go up on 22 November 2026?

Only if your calls ask for expansions. From 22 November X bills each object in includes: users $0.010, and posts, media, polls and places $0.005 each. A call with no expansions costs the same as before.

Does expansions=author_id cost extra on the X API?

Yes, from 22 November 2026. Each distinct author returned in includes.users is a $0.010 user read. The author_id post field alone is just an id on the post.

How many media objects does a post with 4 photos bill?

Four. X's pull request says each media object counts separately, at $0.005, so 4 photos cost $0.020. Dedup still applies: the same media key returned again that UTC day is not charged twice.

How do I avoid X API expansion charges?

Request only the expansions you use. Cache author profiles and look them up once a day, batch user lookups, and watch the Developer Console. Or use a source that returns the author with each post, such as Weir, at 1 credit per post.

Sources

Checked 16 November 2026: