X API
developer.x.com- Category
- Developer Tools
- Rank
- No. 3712Tools index
Previous survey · No. 3539 ·
- Pricing
- Paid
- Type
- TOOL
- Use case
- Business & Commerce
- Interfaces
- API
- Date
About
Developer API for structured X posts, users and authorized account actions. Pay-per-use pricing distinguishes resource reads from action requests. Official Python and TypeScript SDKs, xurl CLI and a live API MCP server offer different integration paths.
At a glance
The X API provides structured access to posts, users and account actions for software that needs more than manually browsing X. It is worth considering for a repeatable research feed, an account-management tool or another narrowly defined integration whose value justifies metered access. The main design choice is what to fetch and how often: reads can be charged per returned resource, so a request that finds hundreds of posts is not priced like a single small lookup.
Good fit
Developers who need filters, pagination and machine-readable results, or authorized actions on an account. App-only authentication can read supported public data; user-context OAuth permits actions within the user’s granted scopes. Official Python and TypeScript clients and the xurl command-line client are documented options. Agents can use the live API MCP endpoint at api.x.com/mcp; docs.x.com/mcp is a different service for documentation search, not access to posts or account actions.
Consider something else when
You only want to read a few posts, need an unrestricted redistributable archive, or cannot tolerate recurring data and policy dependencies. Access does not make every endpoint available under every token, and the developer guidelines restrict uses such as unauthorized model training and require deletion handling. Automation that posts or changes account data also needs appropriate user authority. A read-only integration should not acquire broader account scopes merely because an agent client supports them.
Start here
After obtaining an approved developer app and checking current credit and spending settings, start with a single documented public user lookup: GET /2/users/by/username/xdevelopers using an app-only Bearer token. The expected result is a JSON data object with the account ID, name and username. That is a documented example, not a request performed for this review. For a first search, bound the result count and stop after one page; the recent-search guide covers the last seven days. Automatic SDK pagination can retrieve more billable resources than the first screen suggests.
Cost and requirements
On 31 October 2026, public pay-per-use documentation lists standard post reads at $0.005 per resource and user reads at $0.010. Eligible Owned Reads cost $0.001 per resource only when the authenticated user also owns the developer app and uses a qualifying endpoint. Writes have their own per-request rates. Prepaid credits, optional auto-recharge and a billing-cycle spending limit are separate controls. Published pay-per-use access is capped at three million post reads per cycle; enterprise access differs. Recheck the console quote before committing to a workload.
Limits to know
Endpoint rate limits and credit limits are separate: a positive balance does not prevent a 429 response. Respect the returned reset headers and bound retries. Daily resource deduplication is documented as a soft guarantee, not a reason to assume repeated reads are always free. The live MCP route can be read-only with an app Bearer token; user-context actions use a different authorization path. Credentials, publishing, SDKs, MCP calls, latency, search coverage and actual billing were not tested in this source-based assessment.
Sources checked 2026-10-31. Source-based assessment.
- docs.x.com/make-your-first-request.md
- docs.x.com/fundamentals/authentication/overview.md
- docs.x.com/x-api/getting-started/pricing.md
- docs.x.com/x-api/fundamentals/rate-limits.md
- docs.x.com/x-api/posts/search/quickstart/recent-search.md
- docs.x.com/tools-and-libraries.md
- docs.x.com/tools/mcp.md
- docs.x.com/developer-guidelines.md
Why it made the leaderboard
Useful for a narrowly scoped research or account integration whose benefit justifies metered access and policy obligations. Pagination, ownership-qualified rates, credit limits and account scopes can materially change cost and authority.
Tags
Media
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.