Is the Twitter API Free in 2026? What the Free Tier Allows

Is the Twitter API free in 2026? Not for new developers. Since February 6, 2026, the X API has been pay-per-use: you buy credits and every call draws them down, from $0.001 to read your own data up to $0.20 for a post with a link. Two free options remain. New accounts get a starter allowance of up to $70 in credits, and X still grants free access to apps it approves as "Public Utility" projects.

So is the X API free? You can try it for free, but you can't run it for free. Below: what changed, what the starter credits buy, how to get an X API key, and what the free workarounds cost you in practice.

Is the Twitter API free? the short answer

New signups get no free tier. X's pricing page describes the API as "pay-per-usage pricing with no subscriptions" and lists a price for every endpoint (X API pricing, checked October 2026).

What is free:

• Up to $70 in starter credits, for accounts that are new to paying.
• Free access for Public Utility apps, which X decides case by case.
• The docs, SDKs and a local test server. You can use the official Python and TypeScript SDKs, the Docs MCP and the X API Playground (a local server that mimics the API with mock data) at no cost.

Once the credits run out, every real call against live X data costs money.

What happened to the free tier

X's old free tier was already thin, little more than a posting allowance. In 2025 X pulled the like and follow endpoints from it "to combat abuse, platform manipulation, and fake engagement" (X changelog).

On February 6, 2026, X launched pay-per-use pricing with a new Developer Console. The changelog entry says what free users got: "Recently active Legacy Free tier users receive a one-time $10 voucher." Public Utility apps kept free scaled access. Everyone else moved to credits.

Developers were confused. On r/Twitter, u/aleks__under asked what had happened to "the free basic tier" because "I couldnt find any official info about it." By mid-2026, builder communities had a blunt answer. A developer wiring X into a personal AI agent posted what they had confirmed on r/AI_Agents, u/bettercall_gautam: "X API is pay-per-use, no free tier".

The free credits you can still get

Since October 2, 2026, X has offered pay-per-use accounts two one-time incentives (X free credit incentives):

1. You get $20 when you save your first eligible payment card. Credit and debit cards qualify, but prepaid cards do not. The account must never have made a payment before, and each physical card can earn the credit only once across all accounts.
2. X matches your first auto-recharge, up to $50. Turn on auto-recharge, and when the first automatic top-up succeeds, X adds the same amount in free credits, capped at $50.

A new account that does both gets $70. Three rules apply:

• Free credits expire 3 months after they are granted.
• They are spent before your purchased credits.
• X says the incentives are still rolling out, so some accounts will not see them yet.

X also pays back a share of spend in xAI API credits once you spend $200 or more in a billing cycle. That only helps if you also use Grok's API.

Who still gets free X API access

Public Utility is the one free route left. X's docs describe it as a credit program for "public-good work on the X API". You can't mark your own app as a utility. You publish it and request Public Utility status from the listing, and then X's developer platform team decides. Your app is billed like any other until they approve it.

If you're building alerts for emergencies, transit, public safety or similar civic tools, apply. If you're building a growth tool, a scraper or an outreach bot, plan on paying.

What $20 of free credits actually buys

At October 2026 rates, $20 of credits gets you roughly:

That's enough to build and test a prototype, but not enough to run anything that reads at volume. One developer, u/NHI10 on r/openclaw, let an AI agent loose with a pay-per-use key: "After ~10 minutes and ~1000 tweets from one user, $5 was gone". At that pace, the full $70 lasts a few hours of careless agent use. Set a spending limit before you hand a key to anything automated.

For the complete rate card and four worked monthly bills, see our X API pricing breakdown.

How to get an X API key in 2026

Getting a key costs nothing. Using it costs money.

Step by step

1. Sign in at console.x.com with the X account that will own the app.
2. Create an app, plus a project if the console asks for one. Describe the use case honestly, because X shows it as the source label on posts your app creates.
3. Open "Keys and tokens" for the app and generate what you need (see below). Copy secrets right away, since X shows some of them only once.
4. If you will act on behalf of a user, set the user authentication settings. Enable OAuth 2.0, choose Read or Read and Write permissions, and register a callback URL such as
   http://localhost:8080/callback
   .
5. Add credits or a card. The $20 incentive applies at this step. Live requests are refused until you have a balance.
6. Make a test call. Here is a one-line check with a Bearer token:

curl "https://api.x.com/2/users/by/username/xdevelopers" \
  -H "Authorization: Bearer $X_BEARER_TOKEN"

If you get

Which credentials you need

• Bearer token (app-only): reads public data such as posts, users and search. It cannot act as a user.
• OAuth 2.0 client ID (and secret): lets a user log in and grant scopes such as
  tweet.read
  ,
  tweet.write
  ,
  dm.write
  and
  offline.access
  . Use this to post or DM on someone's behalf today.
• API key, API secret, access token and access token secret (OAuth 1.0a): the legacy user-context method. X still supports it, and in September 2026 it added a token exchange that moves OAuth 1.0a users to OAuth 2.0.

The free workarounds, and what they cost you

When the official API stopped being free, three workarounds filled the gap. None of them charge fees, but you pay for them in other ways.

Scraping libraries such as twikit and twscrape log in as you, using a logged-in session instead of an API key. They break whenever X changes its internals. u/Icy-Care-353 on r/webdev: "I tried twikit, but it's not maintained anymore and full of bugs". Another builder on r/openclaw reported that twscrape was blocked by Cloudflare "almost immediately, even with rotating sessions."

Read-only mirrors are the second option. Nitter-style instances and RSS bridges still exist in places and can read public text. They can't post or send DMs, and they disappear without notice.

The third is reverse-engineered endpoints plus spare accounts. The most candid advice in that r/Twitter thread came from u/symedia: "Reverse engineering their endpoints and use multiple accounts so you don't get banned else you pay".

For a hobby script that reads a few accounts, these routes work, and $0 beats $0.005 per post. The problem is that every one of them breaks X's Terms of Service. The terms say you may not access X except through its published interfaces, and that "crawling or scraping the Services in any form, for any purpose without our prior written consent is expressly prohibited" (X Terms, effective October 9, 2026). The usual consequence is a locked or suspended account, not a lawsuit. If that account matters to you, the "free" route ends up being the expensive one. Our post on whether scraping X is legal goes deeper.

Cheapest paid routes if you need more

Once the starter credits run out, you have three options. Which one fits depends on the job.

• If you're reading your own account's data, stay on the official API. Owned Reads cost $0.001, which keeps dashboards and personal analytics cheap.
• If you're reading public data at volume, a budget third-party read API usually costs far less per tweet than X's $0.005.
• If you're writing across accounts (DMs, follows, likes, posts), use a write-focused API. X removed follows and likes from self-serve plans in April 2026, so the official API can't do part of this job at any price.

That last category is what the XAutoDM API is built for. We'll say it plainly: it isn't the cheapest way to bulk-read tweets. It's built for sending DMs, following, liking and posting across many connected X accounts, and every call is priced in credits: 5 for a read or a follow, 10 for a DM. New signups get 200 one-time credits to test real calls, and paid plans start at $49 a month for 10 connected accounts. It works through connected account sessions rather than X's official API, so keep each account within safe daily limits. The full comparison is in XAutoDM API vs the official X API.

The quickest next step is to open console.x.com, create an app, save a card to claim the $20, and set a spending limit before your first call. If your job is writes across several accounts, create an XAutoDM API key and spend the 200 signup credits on the same test.

Frequently asked questions

Is the X API free in 2026?

No, not for new developers. Since February 6, 2026 the X API has been pay-per-use: you buy credits and pay for each call, from $0.001 to read your own data up to $0.20 for a post with a link. New paying accounts can earn up to $70 in starter credits, and approved Public Utility apps still get free access.

How do I get an X API key?

Sign in at console.x.com with your X account, create an app, and open its Keys and tokens page. From there you can generate a Bearer token for read-only calls, an API key and secret plus an access token for OAuth 1.0a, or an OAuth 2.0 client ID for user login. Add credits before you make any calls, or X will refuse the requests.

Can I still use the Twitter API without paying?

Only within the starter credits, or if X approves your app as a Public Utility. Unofficial routes like scraping libraries cost nothing in fees, but they break often and fall outside X's terms of service, which prohibit scraping without written consent.

What happened to existing free-tier users?

When pay-per-use launched in February 2026, X gave recently active Legacy Free tier users a one-time $10 voucher and moved them onto the credit model. The old free tier, which mostly only allowed posting, is closed to new users.