Fix: X API replies stopped working

The two calls, side by side

Same endpoint, same token, same payload shape. The only difference is whether the account you are replying to summoned you first.

# Works: the author @mentioned you, so you were summoned
curl -X POST https://api.x.com/2/tweets \
  -H "Authorization: Bearer $X_USER_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Thanks for the tag. Here is the short version.",
    "reply": { "in_reply_to_tweet_id": "1893000000000000000" }
  }'

# Refused since 2026-02-23: no mention, no quote, no standing
curl -X POST https://api.x.com/2/tweets \
  -H "Authorization: Bearer $X_USER_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Have you tried our tool?",
    "reply": { "in_reply_to_tweet_id": "1893111111111111111" }
  }'

There is no request field that changes this. No parameter grants standing, and nothing in your app configuration overrides it. Standing is a property of the conversation, not of your credentials.

Where the volume should go instead

A reply bot was never really about replies. It was about being present in conversations at a cadence a human cannot sustain. The February change removes the reply half of that. It leaves the cadence half completely intact.

Three moves recover most of the value:

• Turn the reply into an original post. The take you were going to leave under someone else's post is usually better as a standalone post at a time your audience is actually online. Use your best posting times instead of whenever the trigger fired.
• Turn the thread of replies into a real thread. Self-replies are untouched. A four-post thread you schedule yourself outperforms four replies scattered under other people's posts, and it costs the same.
• Answer summons properly. The replies you can still send are the ones where someone tagged you. Those are the highest-intent conversations you have. Handle them well rather than at volume.

# Threads are self-replies and still work end to end.
# Through OpenTweet it is one call, no X developer account.
curl -X POST https://opentweet.io/api/v1/posts \
  -H "Authorization: Bearer ot_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "We rebuilt our reply workflow after the Feb 2026 X API change. What we learned:",
    "scheduled_date": "2026-09-02T14:00:00Z"
  }'

OpenTweet posts and schedules through your connected X account with no X developer account, no pay-per-use credits, and no per-link surcharge. Threads, originals, and scheduling are all first-class. See the developer docs or connect an agent through the hosted MCP server.