On April 20, 2026, X quietly made one kind of post dramatically more expensive through its API: any post that contains a link.
The numbers, confirmed in X's developer announcement and covered by TechCrunch:
- A plain post via the API went from $0.010 to $0.015 per request.
- A post containing a URL went from $0.01 to $0.20 per request. That is a roughly 1,900% increase, and about 13x the price of a plain post.
X's stated reason is spam. Automated link blasting is the oldest spam pattern on the platform, so X priced the behavior instead of just policing it. The problem is that the fee cannot tell a spam ring from a legitimate changelog bot. If your automation exists to share URLs, and most useful automations do, you are the one paying.
The reaction was immediate and visible. Techmeme, one of the best-known automated accounts on X, stopped putting links in its posts entirely. Its posts now end with "Visit Techmeme dot com for the link and full context!", the domain spelled out in words specifically so it does not count as a URL.
Quick answer: if your bot or agent posts links to X, every one of those posts now bills at $0.20 through the X API. OpenTweet posts the same links for a flat $11.99/mo on Pro, with no per-post fees and no X developer account. Run your numbers →
What actually counts as a link
The fee applies to any post created via the API whose text contains a URL. The important details:
- Your own domain counts. There is no exemption for linking to your own site. A link to your blog, your GitHub release, or your product page bills at $0.20 the same as a link to anywhere else.
- The link-in-reply trick does not dodge it. A reply created through the API is itself a post. If that reply contains a URL, it bills at the link rate too. So "clean post, link in the first reply" costs $0.015 for the post plus $0.20 for the reply, which is more than just putting the link in the post.
- The one carve-out is summoned replies. X's announcement keeps URLs at the old $0.01 price inside summoned replies, meaning replies a bot sends when a user mentions it. That covers ask-a-bot products. It does not cover you replying to your own post with a link.
- Spelled-out domains do not count. "opentweet dot io" is not a URL, which is exactly the loophole Techmeme uses. It also is not clickable, which is the whole problem.
This all sits on top of X's broader pay-per-use model, which became the default for new developers in February 2026. If you want the full pricing picture beyond links, read X API pay-per-use, explained.
Prices shift. Verify current rates on X's official pricing page before budgeting.
The monthly math for a link bot
Almost every genuinely useful X automation is a link automation. An RSS-to-X bot posts links. A changelog bot posts links. A "new blog post is live" workflow posts a link. That is the entire point.
Here is what common patterns now cost per month through the X API, at $0.20 per link post and $0.015 per plain post:
| Automation | Volume | Link posts | Plain posts | Monthly X API bill |
|---|---|---|---|---|
| Changelog bot | 3/day | 90 | 0 | $18.00 |
| RSS/blog bot | 10/day | 300 | 0 | $60.00 |
| Mixed creator agent | 10/day | 100 | 200 | $23.00 |
| News/aggregator bot | 30/day | 900 | 0 | $180.00 |
Compare that middle row to the pre-April world: 300 link posts used to cost about $3. The same behavior now costs $60. Nothing about the bot changed. Only the meter did.
And the fee scales in exactly the wrong direction. The more consistently you publish, the more you pay, and link posts are the ones that drive traffic to your product, your newsletter, your repo. The posts with the most business value carry the highest tax.
Plug your own volume into the X API cost calculator to see your number.
Who this hits hardest
- RSS and blog auto-posters. Every item is a link. A 10-post-per-day feed is $60/mo in link fees alone.
- Changelog and release bots. GitHub release announcements, ship logs, product updates. All links.
- Newsletter and content promoters. The "new issue is out" post is a link post by definition.
- News aggregators. The Techmeme case. At hundreds of posts per day, link fees reach four figures per month, which is why Techmeme removed links rather than pay.
- AI agents that cite sources. An agent that shares what it found, with a URL to the source, pays the link rate on every citation.
Who it does not really hit: casual API users posting occasional text updates, and summoned-reply bots, which got the exemption.
The flat-rate escape hatch
The fee is attached to the X API's meter, not to the act of posting links on X. A human pasting a link into the compose box pays nothing. So the way around the fee is to stop paying per API call and use a posting layer that charges a flat rate.
OpenTweet connects to your X account once (no X developer account, no OAuth code, no token refresh) and gives you a single API key. Posting a link costs the same as posting anything else: nothing extra.
curl -X POST https://opentweet.io/api/v1/posts \
-H "Authorization: Bearer ot_your_api_key" \
-H "Content-Type: application/json" \
-d '{"text":"New post: how we cut our Docker build from 20min to 4min https://opentweet.io/blog/docker-build-optimization-20min-to-4min","scheduled_date":"2026-07-10T15:00:00Z"}'
That is the whole integration. The same key drives a hosted MCP server at https://mcp.opentweet.io/mcp if an AI agent does your posting, and the full REST API supports threads, media, batch scheduling, and analytics.
The comparison for a 300-link-post month:
| X API (pay-per-use) | OpenTweet Pro | |
|---|---|---|
| 300 link posts | $60.00 | $0 extra |
| Monthly cost | Scales with volume | Flat $11.99 |
| Link surcharge | $0.20 per post | None |
| X developer account | Required | Not needed |
| OAuth and token refresh | Yours to maintain | Handled |
| Scheduling | Build it yourself | Built in |
At 300 link posts per month you are already past the price of the flat plan, and the gap widens with every post after that. Pro is $11.99/mo and Advanced is $29/mo; details on pricing. If you want the broader case for skipping X's API entirely, see posting to Twitter without the API.
The bottom line
The $0.20 link fee is a spam control that lands on publishers. It made the most common legitimate automation on X, sharing a link on a schedule, roughly 13 times more expensive overnight, and the biggest automated accounts responded by removing links rather than paying.
You do not have to make that trade. Keep the links, drop the meter:
- Calculate your X API cost at your real volume.
- Understand the full pay-per-use model if you still need the X API for reads or data.
- Start a 7-day free trial and post links at a flat rate, API and MCP included.
Start Scheduling Your X Posts Today
Join hundreds of creators using OpenTweet to stay consistent, save time, and grow their audience.