Build an X alert bot
restocks, price drops, market signals
Alert accounts win on speed. Your watcher detects the event, and one POST to OpenTweet publishes the tweet in seconds. This guide shows the curl call, a six-line Python version, and the MCP option for agent-driven alerts. No X developer account, flat fee.
7-day free trial. No X developer account needed.
What an alert account does
An alert account has one job: be the first to tell its followers that something changed. The pattern is always the same, watch a source, detect an event, tweet it. Only the source differs.
Restock trackers
A product goes from sold out to in stock. Followers who want it get pinged the instant it flips.
Price watchers
A price crosses a threshold or drops by a set amount. The alert fires with the new price and a link.
Market scanners
A ticker, on-chain event, or indicator crosses a level your watcher is tracking. The signal posts in seconds.
Status monitors
A service goes down or recovers. The account becomes the public status feed followers refresh.
The architecture: detect, then POST
Your watcher script or agent polls the source and holds the last known state. When the state changes, it sends one authenticated POST with publish_now set to true, and the alert tweets in seconds. The posting step is a single call, so all your effort goes into the detection, not the plumbing.
The curl call
# Watcher sees a restock, tweets it instantly.
curl -X POST https://opentweet.io/api/v1/posts \
-H "Authorization: Bearer ot_your_key" \
-H "Content-Type: application/json" \
-d '{
"text": "RESTOCK: Acme Runner (size 10) is back in stock.\nhttps://shop.example.com/acme-runner",
"publish_now": true
}'The same thing in Python, six lines
import requests
def tweet_alert(text):
requests.post(
"https://opentweet.io/api/v1/posts",
headers={"Authorization": "Bearer ot_your_key"},
json={"text": text, "publish_now": True},
)Agent-driven alerts over MCP
If an AI agent is doing the watching and the judgment, give it the hosted MCP server. It gets 30 tools for posting, threading, and scheduling, so it can decide what is worth an alert and publish it as a tool call.
{
"mcpServers": {
"opentweet": {
"type": "streamable-http",
"url": "https://mcp.opentweet.io/mcp",
"headers": { "Authorization": "Bearer ot_your_key" }
}
}
}Full endpoint reference in the API docs. Curating a feed rather than firing alerts? See how to build an automated news account.
Why not the official X API
You can build an alert bot on the official X API. It just costs you more setup and a variable bill. Here is the honest comparison.
Official X API
- A developer account you apply for and wait to be approved
- An OAuth app plus tokens you build and refresh yourself
- Per-call billing that a chatty alert bot runs up fast
- You host the scheduling and rate-limit handling
One OpenTweet key
- One bearer key, created after a normal X login
- No OAuth code, OpenTweet owns the connection
- A flat monthly fee, no per-call surprises
- Scheduling, threads, and evergreen on the same key
Full breakdown on OpenTweet vs the X API.
Ship it in four steps
Pick a data source
Choose what to watch: an inventory API or product page for restocks, a pricing feed for price drops, a market API for signals, or a status endpoint for uptime. This is the only part unique to your bot.
Get an OpenTweet key
Sign up, connect your X account once with a normal login, and generate an API key from Settings then API Keys. No X developer account, no OAuth to build.
Wire the POST on event
When your watcher detects the change, send one POST to /api/v1/posts with publish_now set to true. Hold the last known state so you only alert on real transitions, not on every poll.
Add scheduling for filler content
Alerts are bursty. Keep the account alive between them with scheduled posts or an evergreen queue, so followers see a living feed instead of long silences.
An alert bot posts your own original content to your own account, which X allows. Keep it that way: publish alerts and scheduled content, credit sources where relevant, and do not use the account for auto-replies, mass following, or engagement spam, which X bans. OpenTweet posts through an authorized connection, not a scraper.
Frequently asked questions
How do I build a Twitter alert bot?
Run a watcher that checks your data source, and when it detects an event, send one POST to https://opentweet.io/api/v1/posts with your bearer key and publish_now set to true. The tweet goes out in seconds. Your watcher can be a cron script, a serverless function, or an AI agent. OpenTweet handles the connection to X, so there is no OAuth or developer account to set up.
Can I make a restock alert bot for X?
Yes. Poll the product page or inventory API on a short interval, keep the last known status, and when it flips to in stock, fire a single POST to OpenTweet with the product name and link. Because posting is one authorized call, the alert reaches your followers within seconds of the restock.
Do I need the Twitter API for an alert bot?
No. You do not need an X developer account, an OAuth app, or per-call API billing. You connect your X account to OpenTweet once with a normal login, get one bearer key, and post through a REST call or the hosted MCP server. That one key replaces the entire X developer setup.
How fast do the alerts post?
With publish_now set to true, the tweet publishes as soon as OpenTweet receives your request, typically within seconds. The lag that matters for an alert bot is your watcher interval, how often you check the source, not the posting step.
How much does an alert bot cost to run?
OpenTweet is a flat fee: Pro is $11.99/month, Advanced is $29/month, and Agency is $49/month, each with a 7-day free trial. There is no per-call billing, so a chatty alert bot does not run up a variable API bill the way the official X API would.
Everything you can build on X with OpenTweet
Post to X from your code, a watcher, or an AI agent. Start anywhere in the cluster.
OpenTweet vs the X API
Post, schedule, and automate X without a developer account or the $200/mo minimum.
Post to X without an API
The clean, account-safe way to post to X from your code or an AI agent.
Twitter MCP Server
Give Claude, Cursor, and OpenClaw the ability to post to X. 30 tools included.
XMCP vs OpenTweet
X's official MCP server bills per API call and cannot schedule. Compare it with the flat-fee hosted MCP.
MCP for AI agents
Connect your AI client to X in under two minutes, no X developer account.
Developer API and keys
REST endpoints, one bearer key, and usage tracking. Build on OpenTweet.
OpenTweet for AI agents
The posting layer for autonomous agents and automations that live on X.
Build an AI Twitter persona
Give your AI agent its own X account. Setup, cadence, and the rules that keep it safe.
Ship your alert bot today
Connect X, grab your key, and wire the POST. Your first alert can go out in minutes. No developer account, flat fee.
Start your 7-day free trial