Twitter/X
X (formerly Twitter) operates the X Developer Platform, giving developers programmatic access to the public conversation through the X API v2 — Posts, Users, Direct Messages, Lists, Spaces, Communities, Community Notes, Trends, News, Media, and real-time delivery via filtered/sample/firehose streams and webhooks (X Activity, Account Activity, Filtered Stream Webhooks). The platform runs credit-based Pay-Per-Use pricing with a Developer Console at console.x.com, first-party Python and TypeScript XDKs, the xurl CLI, a local Playground mock server, and an unusually deep agent-native surface: llms.txt, AGENTS.md, skill.md, and hosted MCP servers for both the API and its documentation.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Twitter/X the way a machine reads it — 30 machine-readable artifacts across 22 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Twitter/X scores 65.0/100 (strong), with a separate agent-readiness read of 85/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Twitter/X
Each block below is one kind of artifact we hold for Twitter/X. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 22
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Twitter/X Account Activity API
Endpoints relating to retrieving, managing AAA subscriptions
Twitter/X Activity API
The Activity API from Twitter/X — 3 operation(s) for activity.
Twitter/X Articles API
Endpoints related to retrieving, creating & modifying Articles
Twitter/X Bookmarks API
Endpoints related to retrieving, managing bookmarks of a user
Twitter/X Chat API
The Chat API from Twitter/X — 16 operation(s) for chat.
Twitter/X Communities API
The Communities API from Twitter/X — 2 operation(s) for communities.
Twitter/X Community Notes API
The Community Notes API from Twitter/X — 5 operation(s) for community notes.
Twitter/X Compliance API
Endpoints related to keeping X data in your systems compliant
Twitter/X Connections API
Endpoints related to streaming connections
Twitter/X Direct Messages API
Endpoints related to retrieving, managing Direct Messages
Twitter/X General API
Miscellaneous endpoints for general API functionality
Twitter/X Likes API
The Likes API from Twitter/X — 2 operation(s) for likes.
Twitter/X Lists API
Endpoints related to retrieving, managing Lists
Twitter/X Media API
Endpoints related to Media
Twitter/X News API
Endpoint for retrieving news stories
Twitter/X Spaces API
Endpoints related to retrieving, managing Spaces
Twitter/X Stream API
Endpoints related to streaming
Twitter/X Trends API
The Trends API from Twitter/X — 2 operation(s) for trends.
Twitter/X Tweets API
Endpoints related to retrieving, searching, and modifying Tweets
Twitter/X Usage API
The Usage API from Twitter/X — 1 operation(s) for usage.
Twitter/X Users API
Endpoints related to retrieving, managing relationships of Users
Twitter/X Webhooks API
The Webhooks API from Twitter/X — 5 operation(s) for webhooks.
Scroll within the panel for all 22 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
twitter-x-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Twitter X Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Twitter X Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Twitter/X — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/twitter-x · machine-readable index on apis.io