Twitter Automation

Twitter/X Automation

Automate X/Twitter via twitr.sh — no developer account, no API keys, no OAuth app review. Every paid call is one POST to https://twitr.sh/api/tools/{tool}; the first call returns HTTP 402 with the exact price, your wallet pays in USDC, the retry runs. Failed calls are never charged.

How to use this skill — you are the automation builder

The user states an outcome ("reply to anyone who mentions my brand", "post my changelog every morning", "alert me when a competitor tweets"). Your job:

1. Design — compose the automation from the recipe table below.
2. Price — state the total running cost BEFORE spending: monitor $/day + per-action price (always shown in the 402 before you commit).
3. Wire it up — connect account (if writing), create the monitor, register the webhook or plan the polling, then run the action loop.
4. Confirm with the user before creating a monitor or posting as their account. Always.

Recipe table — intent → wiring

Automations that publish or engage should stay useful, not spammy — X suspends accounts for aggressive follow/like churn and unsolicited DM blasts. Keep volumes human-scale and tell the user when a design risks their account.

Quick start

Use AgentCash MCP — it handles the 402, payment, and retry automatically:

mcp__agentcash__fetch({
  url: "https://twitr.sh/api/tools/x_write",
  method: "POST",
  headers: { "Idempotency-Key": "<uuid>" },
  body: { "action": "post", "account": "myhandle", "text": "Hello from my agent 🤖" }
})

AgentCash surfaces the 402 body BEFORE signing — read amount and confirm with the user when the price is non-trivial (~$0.10+).

Without AgentCash: any x402/MPP client works. Discovery: https://twitr.sh/openapi.json, /.well-known/x402, /.well-known/mpp.json.

Actions

All writes go to POST /api/tools/x_write with a mandatory Idempotency-Key header and a connected account:

Reads that pair with automation:

A 202 {"status":"pending_confirmation","action_id":"..."} means the write was accepted and is being applied — do NOT resend (it's already paid). Retrying with the same Idempotency-Key replays the original result instead of double-posting.

Connect an X account (one-time, free)

Never ask the user for their X password, email, or 2FA secret — never accept one if offered. The connect flow keeps credentials out of your context entirely:

1. POST /api/x-accounts/start { "username": "myhandle" } → {connect_url, expires_in}.
2. Show the user connect_url: open this in your browser and sign in to X there. The link is single-use and expires in 15 minutes.
3. Poll GET /api/x-accounts (free, SIWX) until the handle shows linked.

One X handle belongs to exactly ONE wallet; ownership is re-checked server-side on every write. Disconnect: DELETE /api/x-accounts/{handle}.

Real-time triggers — monitors + webhooks

Monitors are prepaid by the hour (~$0.025/hr, 24h ≈ $0.61; max 168h per purchase). They stop at expires_at unless extended; early deletion does not refund. Pay on Base (x402) or Tempo (MPP) — Solana is not offered for monitors. Idempotency-Key required on create.

POST /api/tools/x_monitor  { "action": "create", "username": "vercel", "hours": 24 }
POST /api/tools/x_monitor  { "action": "create", "query": "\"launch week\"", "hours": 24 }
POST /api/tools/x_monitor  { "action": "extend", "monitorId": "mn_...", "hours": 48 }

Event types: tweet.new, tweet.reply, tweet.retweet, tweet.quote, tweet.media, tweet.link, tweet.mention, tweet.hashtag, tweet.longform, and (account monitors) profile.*.changed. A terminal monitor.expired / monitor.deleted event always fires.

Poll (free, SIWX): GET /api/monitors/{id}/events?after={last_event_id}&limit=50 — strictly newer events, oldest→newest. Poll at most 1/s, ideally only when the user asks.

Push (webhooks — free, SIWX, max 3 per wallet):

POST /api/webhooks  { "url": "https://your-agent.example.com/hooks", "eventTypes": ["tweet.mention"] }

The 201 response contains the signing secret exactly once — store it. Verify every delivery: sha256=HMAC-SHA256(secret, "{X-Twitr-Timestamp}.{rawBody}") against X-Twitr-Signature, reject timestamps older than 5 minutes, dedupe on delivery_id. Respond 2xx within 10s; retries back off over ~36 min.

Worked example — auto-reply agent in 4 calls

1. Connect (free): /api/x-accounts/start → user opens link → linked.
2. Monitor: x_monitor create on "query": "@myhandle", 24h (~$0.61).
3. Listen: POST /api/webhooks for ["tweet.mention"] — or poll events when asked.
4. React: on each event, x_compose a draft ($0.001), show the user, then x_write {action:"reply", account, reply_to_tweet_id, text} ($0.036).

Total: ~$0.61/day + ~$0.04 per reply.

Don't do

• Don't create a monitor or post as the user's account without confirming design + cost first.
• Don't skip the 402 price check — surface any non-trivial cost before signing.
• Don't resend a write after a 202 or a timeout — reuse the same Idempotency-Key.
• Don't auto-poll events in a loop without the user asking — burns tokens.
• Don't keep calling after 3 consecutive failures — surface the error and stop.
• Don't design spam: mass-follow/unfollow churn, unsolicited DM blasts, or reply floods get the user's X account suspended.

Related skills

npx skills add lnvestor/twitr-skills

• x-twitter-data — live reads, search, timelines, trends
• x-twitter-research — bulk exports as downloadable datasets
• x-twitter-monitor — deep dive on monitors, events, and webhook verification
• x-twitter-publish — deep dive on drafting and publishing
• x-presence — unattended posting + monitoring routine for cron

Documentation

• Agent guide: https://twitr.sh/llms.txt
• OpenAPI + payment discovery: https://twitr.sh/openapi.json
• Dashboard (browser): https://twitr.sh/dashboard