BuzzyX

X API expansions start costing money on 22 November: what founders should check

Divv SaxenaPublished Last updated 9 min read

X API expansions stop being free from 22 November 2026: per expanded object, a User costs $0.010 and a Post, Media, Poll or Place costs $0.005 on the pay-per-use plan The objects you pull in with expansions get their own line on the bill.

On 22 November 2026, X starts charging for something that has been free: X API expansions. If your app asks for a post and also pulls in its author, its images or the post it quotes, those extra objects get billed from that day. A user costs $0.010. A post, media item, poll or place costs $0.005 each.

X announced this in its developer forum on 23 October. A later staff reply lists the same rates, but they still aren't on X's docs or changelog. I build BuzzyX on the X API, so I read the announcement, X's docs and the staff replies around it today, 13 November 2026. Here's what an expansion is, the math, who should worry and how to cut the bill before the 22nd.

What an X API expansion is

When you ask the X API for a post, you get a small object back. X's fields guide says a post lookup returns only the ID, the text and the edit history IDs by default. If you want to know who wrote it, you have two choices.

You can ask for tweet.fields=author_id. That adds the author's ID to the post. Just a number.

Or you can ask for expansions=author_id. Then X sends the whole user object (name, handle and any user fields you asked for) in a separate includes section of the same response. X's expansions guide pitches this as getting related objects "in one call" instead of making more requests.

Diagram of an X API request with expansions=author_id: the post comes back in data and is billed $0.005, the author's user object comes back in includes and is billed $0.010 from 22 November The post sits in data. The expanded author sits in includes, and that's the part that starts costing money.

Authors aren't the only expansion. The same guide lists ones for quoted and replied-to posts, mentioned users, images and videos, polls, places and older versions of edited posts.

What changes on 22 November

On the pay-per-use plan, X bills reads per object returned, not per request. Its pricing page says reads are "charged per resource returned in the response." The catch was that objects in includes weren't being counted. In the announcement, X staff wrote: "Right now, objects that come back through expansions aren't counted towards usage."

From 22 November they will be, "at the standard PPU rate for that resource, the same as direct lookups." These are the rates X posted:

Object in includes Rate per object
User $0.010
Post $0.005
Media $0.005
Poll $0.005
Place $0.005

Rate card for X API expansion objects from 22 November 2026: User $0.010, Post $0.005, Media $0.005, Poll $0.005, Place $0.005, with Media, Poll and Place not yet on X's pricing page as of 13 November Users cost twice what posts do. Media, poll and place have no row on X's pricing page yet.

Screenshot of the X developer forum post X API PPU Expansions Update by X staff, saying expansion objects bill at the standard rate from November 22nd, with the rate table for Post, User, Media, Poll and Place The original post on X's developer forum, so you can check the numbers yourself.

In a 28 October staff reply in a follow-up thread, X added three details:

  • Each media object counts on its own. A post with four images bills four media objects.
  • The 24-hour UTC deduplication covers everything in includes, not only posts. If the same user comes back twice in one UTC day, you pay once.
  • On true owned reads (your own app reading your own posts, mentions or likes), expanded objects bill at $0.001, like the posts. If your customers sign in to your app, that's not an owned read, and everything bills at the standard rates.

As of today, X's pricing page still has no row for Media, Poll or Place, though staff said they're adding them. X's changelog has no entry for this either. X-Autopilot has a longer writeup if you want more on the edge cases.

One odd thing. Two earlier staff replies, from August and September, already said expanded objects count. The October announcement says they haven't been. I'm going with the newer, official post. Your Developer Console after the 22nd will settle it.

A worked example: one search, before and after

Here's the kind of call tools make all day: a recent search that returns 100 posts, with expansions=author_id.

Before 22 November, you pay for the posts:

  • 100 posts × $0.005 = $0.50

After 22 November, it depends on how many different people wrote them. The September staff reply says a user usually appears once per response even if they wrote several of the posts. So you pay per distinct author:

  • 100 different authors: $0.50 + (100 × $0.010) = $1.50
  • 40 different authors: $0.50 + (40 × $0.010) = $0.90

Now add two extras a lot of tools ask for. Say 30 of those posts have one image and 20 quote another post, and you expand both:

  • Images: 30 × $0.005 = $0.15
  • Quoted posts: 20 × $0.005 = $0.10
  • Total with 100 different authors: $0.50 + $1.00 + $0.15 + $0.10 = $1.75

Worked example of a 100-post X API search after 22 November: 100 posts $0.50, 100 distinct authors $1.00, 30 images $0.15, 20 quoted posts $0.10, total $1.75 versus $0.50 before Same request, same results. 3.5 times the price.

That's 3.5 times the old bill for the exact same request. The number that moves your cost isn't how many calls you make. It's how many different people show up in your results.

Now scale it to a month. Say a monitoring tool pulls 1,000 new posts a day from 600 different authors. Before: $5.00 a day. After: $5.00 + (600 × $0.010) = $11.00 a day. Over 30 days, $150 becomes $330. I made up those volumes to show the math, but every rate in it is X's.

Before and after card for a hypothetical monitoring tool reading 1,000 posts a day from 600 authors: $150 a month until 21 November, $330 a month from 22 November with author expansions A made-up monitoring tool, priced with X's real rates.

Who this hits

If you only use x.com, nothing changes for you. This is about apps on X's pay-per-use API plan that read posts. It stings most when:

  • You search or monitor keywords and show the author next to each post. Social listening, reply finders and lead tools all do this.
  • Your results come from lots of different people. Strangers mean many distinct users, and users are the expensive object.
  • You expand media on image-heavy feeds, since every image counts.
  • You read your customers' timelines after they sign in to your app. X staff confirmed those reads bill at standard rates, not the $0.001 owned rate.

It stings less when the same few accounts show up again and again in one UTC day, because deduplication kicks in. Posting isn't part of this change at all.

For BuzzyX, I already priced a Discover search as ten posts plus ten author profiles at $0.010 each when I wrote up what the X API costs per call. So this change mostly matches the math we planned around. If you priced your product on expansions being free, redo that math this week.

How to cut your X API expansions bill

X's own advice in the announcement is short: check "which fields and expansions your requests use and optimize accordingly," and watch the Developer Console. Here's what that looks like in practice, based on X's docs and staff answers.

Six ways to cut an X API expansions bill: drop expansions you don't show, use fields when an ID is enough, read mentions from entities, cache users across days, batch syncs in one UTC day, set a spending limit Six fixes you can ship before 22 November.

  1. Drop expansions you don't show. A staff reply put it plainly: "Don't request expansions you won't use." Search your code for expansions= and check each one against what your UI actually renders.
  2. Use fields when an ID is enough. Per the same reply, tweet.fields=author_id only adds the ID and is still one post read. If you only group or filter by author, you don't need the full user.
  3. Read mentions from entities. tweet.fields=entities returns each mention with its username and ID, according to X's API spec. The entities.mentions.username expansion adds a full user object at $0.010 each on top.
  4. Cache users across days. Deduplication resets at midnight UTC. Keep the names, handles and avatars you've already paid for, and look up only new IDs with user lookup, which takes up to 100 IDs per call. New users still cost $0.010, but you stop paying for the same person every day.
  5. Run repeat syncs inside one UTC day. Two syncs of the same timeline in the same UTC day bill each object once. The first sync after midnight UTC starts fresh.
  6. Set a spending limit. The pricing page lets you cap spend per billing cycle in the Developer Console. Set it before the 22nd, then check your usage daily that week.

What X still hasn't said

  • Whether expanded posts count toward the 3 million post reads a month cap on pay-per-use. The pricing page mentions the cap. The announcement doesn't.
  • When the Media, Poll and Place rows will show up on the pricing page.
  • Whether the usage endpoint, which returns daily post consumption, will show expanded users or media. I couldn't find it written down, so I'd trust the console.

For the full read and write rate card, see my X API pricing guide. If you're building reply features, the X API reply restriction is the other rule worth knowing this year.

Grow on X without running the API yourself

If you'd rather spend your time writing posts than auditing includes, that's what BuzzyX is for. It's one $29 plan with daily caps sized so no account costs more than it pays, and you still press send on every reply.

Start your 7-day BuzzyX trial

FAQ

Are X API expansions free?

Until 21 November 2026, objects returned through expansions aren't counted on pay-per-use, per X's announcement. From 22 November they bill at the standard rate for each object.

How much does an expanded user cost on the X API?

$0.010 per user, the same as a direct user lookup. Posts, media, polls and places cost $0.005 each.

Do fields cost extra?

No. X staff said tweet.fields=author_id only adds the ID and is still one post read. You pay per object, so fields that add data to an object you already get don't add a charge.

Does the 24-hour deduplication apply to expansions?

Yes. X staff said it covers every billable object in includes, including users, media, polls and places, within the same UTC day.

BuzzyX · X growth workspace

Grow on X with posts that sound like you.

Compose in your voice, schedule the week, find posts worth replying to and read real analytics from the X API. $29/mo after the trial, everything included.

Try BuzzyX free →See pricing7-day free trial. Card required, $0 today, cancel in Settings.

Share

All posts →

All posts