Twitter / X API for AI agents — UnifAPI
UnifAPI’s Twitter / X API gives an AI agent server-side access to public Twitter data — tweets, users, timelines, replies, search — through one normalized HTTP endpoint, billed per call.
- Live page: unifapi.com/apis/twitter
- Auth: one bearer key, no per-user OAuth
- Pricing: pay-per-call credits
- MCP tools: exposed via the hosted MCP server as
twitter.*
Endpoints (v1)
| Endpoint | Description |
|---|---|
twitter/users/lookup | Get a user’s profile by username or id |
twitter/users/tweets | Fetch a user’s recent tweets |
twitter/tweets/get | Fetch a single tweet by id |
twitter/tweets/replies | Replies to a tweet |
twitter/search | Search tweets by query / filters |
twitter/users/followers | A user’s followers (where public) |
twitter/users/following | Who a user follows |
Example
curl https://api.unifapi.com/v1/twitter/search \
-H "Authorization: Bearer $UNIFAPI_KEY" \
-d '{"q": "ai agents", "since": "24h", "lang": "en"}'
What it’s for
- Social listening — brand mentions, sentiment
- Trend discovery — what people are talking about
- Creator discovery — find and score creators
- Competitive intelligence — track competitor announcements
- Lead enrichment — public social footprint of a company
Why UnifAPI’s Twitter API
The official paid API tier is expensive and rate-locked. Most agent builders end up wiring a third-party scraping vendor — at which point you’re juggling N vendors. UnifAPI gives you one bearer key, one normalized shape, MCP-ready tool definitions, and pay-per-call billing.
Alternatives compared: UnifAPI vs RapidAPI · vs Apify