How to schedule X (Twitter) posts with an AI agent — drafts, approvals, edits and real costs
An AI agent can run your X posting end to end — drafting, scheduling, publishing and measuring — while a person approves every post that goes public. X's API has no drafts and no scheduling, and it bills every request, so the queue, the approvals and the cost need a plan. This guide covers each.
1. Connect your X profile
- 1On Integrations, press Connect on the X Organic card and authorize the app on X. It asks to read and write posts, read your profile, upload media and stay connected.
- 2Once per app, the administrator registers the callback on the X app with Read and write permission and buys pay-per-use credits in the X Developer Console — without credits X refuses every request.
- 3Ask the agent to check the connection: it lists what the connection may do (post, edit, delete, read metrics) before it tries anything.
2. Draft posts that fit X's limit
- 280 weighted characters. A link always counts as 23 characters however long it is, and CJK characters and emoji count double — the agent measures every draft the way X does and flags one that is over.
- Ask for variants: "three posts about our launch, one with a question, no hashtags" returns drafts with their length, nothing posted.
- Drafts live in Agent Planners. X has no draft or hidden post through its API, so a draft is kept in the queue until a person approves publishing it.
3. Schedule through the queue
X's API cannot schedule a post, so Agent Planners keeps its own queue and publishes each approved post at its time. The same queue serves the app, agents, Codex or Claude over MCP, the REST API and projects — a post already queued or published for the account is reused rather than created again, and a send whose result is uncertain (a timeout after the request left) is checked against your recent posts before anything is retried. A post is never sent twice.
4. Approvals: who decides what goes public
- Publishing, scheduling, editing and deleting always wait for a person — whatever the approval setting, even with auto-approve on, and from an API key or MCP client.
- Reading, drafting and cancelling follow your normal approval setting: by default every change waits for your approval, and auto-approve is opt-in.
- Forbidden Rules apply: a rule that blocks posting for an account blocks it on every lane.
5. Edits have a window
- X allows an edit only within a window it sets per post — 30 minutes in X's documentation; the posts we measured on a live account carried a one-hour window. The agent reads each post's own deadline rather than guessing.
- At most five edits, and each edit creates a new post id. Deleting any version deletes the whole chain.
- Replies to other people's posts, polls and reposts cannot be edited (X's rule).
6. Measure what you posted
- Recent posts come back with impressions, likes, replies, reposts, quotes and bookmarks.
- Ask for a weekly summary or a schedule that reads them every Monday; a project shows each of its posts with the outcome.
7. From Codex or Claude over MCP, or your own system over REST
- MCP: connect Agent Planners to Codex or Claude and use the social__* tools — social__list_accounts, social__generate_post, social__create_draft, social__schedule_post, social__publish_post, social__list_posts, social__get_post_insights. Approvals still apply.
- REST: POST /api/v1/tools/social__schedule_post with the account id, the text and the time; a write that waits for a person answers 202 with the request to poll.
8. What it costs
Prices are X's published pay-per-use rates (docs.x.com, read on 26 October 2026; X notes they can change). Agent Planners bills a call only when X accepted it, never twice for a retry, and the credit price keeps at least a 70 % margin over X's cost on every plan. Each tool call also carries the usual small per-call charge.
| X API call | X's price | Agent Planners credits |
|---|---|---|
| Post created | $0.015 per request | 100 |
| Post created with a link | $0.20 per request | 1,334 |
| Post read (any post, your own included) | $0.005 per post | 34 per post |
| Profile read | $0.010 per user | 67 |
| Delete | $0.010 per request | 67 |
Frequently asked questions
- Can an AI agent schedule tweets?
- Yes. X's API has no scheduling, so Agent Planners' queue publishes each approved post at its time and never sends the same post twice.
- Will the agent post without asking me?
- No. Publishing, scheduling, editing and deleting always wait for a person's approval, even with auto-approve on and from an API key.
- Can I edit a post after it is published?
- Within X's edit window for that post — 30 minutes in X's docs, an hour measured on a live account — up to five times; each edit is a new post id.
- How much does posting to X through the API cost?
- X charges $0.015 per post, $0.20 per post with a link and $0.005 per post read; Agent Planners bills about 100 credits per post and 1,334 with a link, only for calls X accepts.