Profiles, posts, comments and search: 10 APIs from 1 credit per call.
The APIs
Prices are in credits, per call, and the same on every plan. A call that fails costs nothing.
1 more planned. Community search.
The official API
X’s own API, still called the Twitter API by many developers, reads and publishes posts, users, lists, Spaces, DMs and trends through v2 REST endpoints. Anyone with an X account can create an app in the Developer Console; self-serve use is paid from prepaid Pay-Per-Use credits, and the highest-volume endpoints need an Enterprise plan.
As of 2026-11-14, X sells self-serve access only as Pay-Per-Use credits bought upfront in the Developer Console, with no contract, subscription or minimum spend.
Read on X API pricing (docs.x.com) (opens in a new tab)Reads are billed per resource returned: $0.005 for each post and $0.010 for each user or follower record (as of 2026-11-14). Creating a post costs $0.015, or $0.200 when it contains a URL.
Read on X API pricing (docs.x.com) (opens in a new tab)As of 2026-11-14, Pay-Per-Use is capped at 3 million post reads per monthly billing cycle, and X sells higher volume as Enterprise plans.
Read on X API usage and billing (docs.x.com) (opens in a new tab)An app’s Bearer Token gives app-only, read-only access to public data. Posting and DMs need OAuth 2.0 or OAuth 1.0a user tokens (as of 2026-11-14).
Read on Getting access (docs.x.com) (opens in a new tab)Since Pay-Per-Use launched on 2026-02-06, free scaled access has been limited to apps X classes as Public Utility Apps.
Read on X Developer Community: Pay-Per-Use launch, 2026-02-06 (opens in a new tab)X is retiring OAuth 1.0a user authentication: apps have until January 31, 2027 to move to OAuth 2.0, after which requests signed with OAuth 1.0a stop working.
Read on OAuth 1.0a token exchange (docs.x.com) (opens in a new tab)Checked against X’s developer docs (opens in a new tab).
Yes. The X API, formerly the Twitter API, has v2 REST endpoints for posts, users, lists, Spaces, DMs and trends. You get access by creating an app in the X Developer Console and paying for usage with prepaid credits.
Not for most apps. Self-serve access runs on prepaid Pay-Per-Use credits, and free scaled access is limited to apps X classes as Public Utility Apps. New pay-per-use accounts can earn one-time free credits, which expire three months after they are granted.
X charges for each post, user or follower a read returns and for each write request, at the rates on its pricing page, from credits you buy upfront. Post reads stop at 3 million per monthly billing cycle unless you move to an Enterprise plan.
Sign in at console.x.com, accept the Developer Agreement and Policy, describe how you will use the API and create an app. The console shows your API Key and Secret, Bearer Token and OAuth credentials only once, so save them right away.
Yes, for public data. PrimaryAPI’s X APIs return public profiles, posts, replies and follower lists as JSON with your PrimaryAPI key, so there is no X app to create and no X credits to buy. Posting and DMs still need X’s own API.
Many developers search for an X scraper when what they need is public X data as JSON. PrimaryAPI serves public profiles, posts, replies and followers through documented APIs with a price per call, and you only pay when data comes back.
Yes. An agent can connect to PrimaryAPI’s MCP server or read its SKILL.md, start on a capped trial key, and keep calling the X APIs once a person approves a spend limit.
Create an account, buy credits when you need them, and call every X / Twitter API with the same key.