MENTIONS
Twitter Mentions API: Monitor Any Account at $0.04/1K
The Twitter Mentions API is a REST endpoint that returns every public tweet mentioning any account as paginated JSON at $0.0008 per call ($0.04 per 1,000 results). Poll on a schedule with a since_id anchor for near-real-time brand monitoring, support triage, and AI-agent inboxes, on one Bearer key, no developer account, no platform rate limits.
What is the Twitter Mentions API?
Endpoint: GET /twitter/user/mentions. Pass any public userName and receive an array of tweets that mentioned that account, sorted newest first. Each tweet includes the full text, author, timestamp, conversation ID, and public metrics. The response carries a next_cursor and has_more for cursor pagination, plus a since_id anchor you store to make every subsequent poll incremental. Cost: $0.0008 per call, or about $0.04 per 1,000 mentions pulled. No X developer account required.
What you can build with mentions monitoring
Mentions are the inbound firehose for any public account. The same endpoint and the same Bearer key power every pattern below, billed flat at $0.0008 per call regardless of how many mentions the response contains.
| Use case | What to pull | Why it matters |
|---|---|---|
| Brand monitoring | Catch every public tweet that tags your handle | React before negative sentiment spreads |
| Customer support triage | Route inbound @mentions to your helpdesk queue | Faster SLA, no manual tab-watching |
| Influencer tracking | Log mentions of a partner or competitor handle | Attribution and earned-media measurement |
| Event listening | Capture mentions of a campaign hashtag account in real time | Live leaderboard or UGC aggregation |
| AI agent inbox | Feed mentions into an LLM classification pipeline | Auto-tag intent, sentiment, and escalation priority |
For tweet-level search by keyword or hashtag rather than account handle, use the Twitter search API. Mentions and search share the same key and the same flat billing.
Pull mentions with a since_id polling loop
The mentions endpoint lives at GET /twitter/user/mentions. On the first call, omit since_id to get the most recent mentions. Store the highest tweet ID you see. On every subsequent call, pass that stored ID as since_id and the API returns only tweets posted after it, keeping each poll incremental and cost-efficient.
First pull + ongoing polling loop
1# First pull: latest mentions of @yourhandle2curl -H "Authorization: Bearer YOUR_API_KEY" \3 "https://api.twitterapis.com/twitter/user/mentions?userName=yourhandle"45# Subsequent calls: only new mentions since tweet ID 18000000000000000006curl -H "Authorization: Bearer YOUR_API_KEY" \7 "https://api.twitterapis.com/twitter/user/mentions?userName=yourhandle&since_id=1800000000000000000"Each call costs $0.0008. A 60-second polling loop runs about 1,440 calls per day, which is $1.15 per day or about $34.56 per month. Stretching the interval to 5 minutes drops monthly cost to $6.91 with no code changes beyond the sleep duration. Read the mentions endpoint docs.
Polling interval vs cost: pick your cadence
Every poll is one call at $0.0008, regardless of how many mentions the response contains. The only cost lever is how often you poll. Match your interval to the freshness your use case actually requires.
| Poll interval | Calls / day | Calls / month | Cost / month | Best for |
|---|---|---|---|---|
| Every 60 s | 1,440 | ~43,200 | ~$34.56 | Near-real-time support queues, high-volume brand accounts |
| Every 5 min | 288 | ~8,640 | ~$6.91 | Moderate brand monitoring, competitor tracking |
| Every 15 min | 96 | ~2,880 | ~$2.30 | Low-volume accounts, research ingestion pipelines |
| Every 1 hour | 24 | ~720 | ~$0.58 | Periodic audits, daily digest aggregators |
Monitoring multiple accounts multiplies costs by the number of handles. See the full breakdown on the Twitter API pricing page.
TwitterAPIs mentions vs the official X API and manual watching
| Option | Price | Auth | Limits | Near-real-time |
|---|---|---|---|---|
| TwitterAPIs | $0.04 / 1,000 mentions | Bearer token, 30 s signup | No rate limits | Poll every 60 s |
| Official X API user/mentions | Gated, paid enterprise tier | X developer account, app approval | Hard request caps on every tier | Streaming only on enterprise |
| Manual browser monitoring | $0 plus your time | None | Manual, misses fast threads | Not real time |
Pricing, plain and flat
$0.04
per 1,000 mentions returned
$0.50
free credits at signup, no card
$0
subscription, you pay per call only
There is no minimum spend and no monthly seat fee. You start with $0.50 in free credits and pay $0.0008 per call after that. See the full breakdown on the Twitter API pricing page, or explore the full API docs.
Wire mentions into an AI agent via MCP
Install the TwitterAPIs MCP server (@twitterapis/mcp) and the mentions endpoint becomes a native tool call any MCP-compatible model can invoke. The same Bearer key authorizes every call, so you add one line to your MCP config and your agent gains a live mention feed with no extra code. For keyword-based search instead of account-based listening, the Twitter search API runs on the same key. To pull an account's full posting history instead of only its mentions, use the Twitter timeline API. To get the follower graph of accounts that mention you, combine with the Twitter followers API. Need a key? Get a Twitter API key in 30 seconds.
Twitter mentions API FAQ
GET /twitter/user/mentions returns a paginated array of public tweets that mention the given account. Each tweet object includes the full tweet text, author details, timestamp, public metrics (likes, retweets, replies, views), conversation ID, and whether the tweet is a reply or a quote. The response also carries a next_cursor and has_more flag so you can walk multiple pages of older mentions, and a since_id anchor so each polling cycle only returns new tweets since the last call.
Each call is $0.0008 (source: twitterapis pricing). If you poll once per minute around the clock that is 1,440 calls per day, or about 43,200 per month, which works out to $34.56 per month. Polling every 5 minutes drops that to $6.91 per month. There is no subscription, no monthly minimum, and you start with $0.50 in free credits at signup. The official X API gates user mentions lookup behind paid developer tiers with hard request caps; TwitterAPIs charges only for what you actually pull.
since_id is a tweet ID string you pass on every polling call after the first. The API returns only mentions posted after that tweet ID, so your pipeline is incremental: each cycle you pull exactly the new mentions and nothing you already processed. Without it every poll returns the full recent history and you have to de-duplicate on your side. Store the highest ID you see after each call and pass it as since_id on the next one.
Install the TwitterAPIs MCP package (@twitterapis/mcp) and add your Bearer token to your MCP config. The MCP server exposes user/mentions as a native tool call, so Claude, GPT, or any MCP-compatible model can fetch a live mention feed in a tool turn with no extra code. For custom agent stacks, call the REST endpoint directly from a tool-use handler and pass the result to your LLM classification step.
Call GET /twitter/user/mentions with the userName you want to monitor and store the highest tweet ID you see. On every subsequent call, pass that ID as the since_id parameter. The API returns only tweets posted after that ID, so each poll is incremental and you never re-process a mention. Call every 60 seconds for near-real-time coverage ($0.0008 per call, about $34.56 per month at that cadence) or every 5 minutes for moderate monitoring ($6.91 per month).
No. You do not need an X developer account or any OAuth setup. You need only a TwitterAPIs key, which is a single Bearer token you copy after a 30-second signup. No app review, no waiting period, no X approval. You can start pulling mentions within a minute of registering.
Yes. Omit since_id and use the cursor pagination instead. Each response includes a next_cursor and a has_more flag. Pass next_cursor back on the next call to walk backwards through older mentions. Use cursor pagination for historical backfills (auditing the last 30 days of mentions, for example), and switch to since_id polling for the live monitoring loop once you have ingested the history.
Monitor mentions without an X account
$0.04 per 1,000 mentions. $0.50 free credits. since_id polling, no developer account, no rate limits.
Next read
Continue exploring related pages:
Twitter API use cases
14 use cases from sentiment analysis to lead generation.
Twitter timeline API
Pull an account's full posting history over one REST endpoint.
Twitter list API
Read list members and list timelines with the same Bearer key.
TwitterAPIs pricing
Brand pricing page with endpoint-level costs and quick totals.