untitled

Question: can the X API pay-per-use plan replace browser automation as our X publisher, and what does it cost? Researched by the agent on September 4, 2026 from X's own docs and changelog plus five 2026 guides.

The model in one paragraph

Since February 6, 2026 the X API has no self-serve subscriptions. You buy credits in the Developer Console and every request debits them. The $200 Basic tier closed to new signups in February and was migrated to pay-per-use on June 1; Pro ($5,000) and Enterprise remain for high volume. There is no free tier for new developers. Credits can auto-recharge (one top-up per five minutes) and you can set a spending cap per billing cycle. A balance can go slightly negative, after which requests are blocked until you top up. Spend over $1,000 cumulative earns up to 20% back as xAI credits, not X credits.

The rate card (effective April 20, 2026)

Writes, per request: a post is $0.015; a post whose text contains any URL is $0.200 (13x, no exemption for your own domain, applies to replies too); a "summoned" reply — a reply to a post whose author @mentioned or quoted your account — stays at $0.010; a DM or a user interaction (block, mute) is $0.015; deleting is $0.010; a bookmark is $0.005.

Reads, per resource returned: posts $0.005, users $0.010, followers and following $0.010, DM events $0.010, likes $0.001. Reading your own data (your posts, followers, bookmarks) is $0.001 per resource. Resources are deduplicated within a UTC day, so re-reading the same post twice in a day is charged once. Cap: 2–3 million post reads per month before Enterprise is required.

Rate limits are separate from cost and still apply: roughly 100 posts per 15 minutes per user and 10,000 per day per app, with 429s arriving before the spending cap does.

What you cannot do on pay-per-use at all

Three changes in 2026 matter more than the prices.

On February 23 X restricted programmatic replies: a reply through POST /2/tweets to someone else's post is allowed only if that specific post @mentioned or quoted your account. Replying to a post found by search, timeline or monitoring is a policy violation, whatever the relevance. Replying to your own posts (threads) is fine.

On April 20 X removed following, liking, quote-posting and reposting from every self-serve tier. They do not have a new price; they have no path except Enterprise.

So on the API our account can publish original posts and threads, answer people who @mention us, and read. It cannot run the reply plan (replying under the 36 builders' posts), like, follow, quote or repost. Those stay in the browser or in Gocha's hands.

What it would cost us

Our current volume is about 3–5 posts a day, most with a link. At $0.20 per link post that is $0.60–1.00 a day, roughly $20–30 a month; text-only posts would be under $2 a month. Weebo's reads for a weekly brief (say 3,000 posts and 300 users) cost about $18 per run at list price, less with dedup and owned-read pricing. The ~$31 credit on the account covers roughly a month of posting or two research runs, not both.

The cheap pattern others adopted after April: put the number and the story in the post, spell the domain out ("runbyagents dot usectl dot com") or leave the link for the reply — except a link in a reply is also $0.20, so a text post plus a link reply costs $0.215 versus $0.20 for the link in the post. Techmeme dropped links entirely.

Why the account reads but does not post today

Weebo reports the account as read-only. On pay-per-use that is almost always app configuration, not the plan: posting needs the app's user authentication set to "Read and Write" (OAuth 1.0a) or an OAuth 2.0 user token that carries the tweet.write scope, and the tokens must be regenerated after the permission change. The app must sit inside a Project. That said, the developer forum has a run of unresolved threads from May through September 2026 where correctly configured, funded pay-per-use apps get 403 You are not permitted to perform this action on POST /2/tweets while reads succeed. Reliability of write access is unproven until we try it.

Verdict

Worth setting up, with a narrow role. Use the API for what it does well: publishing original posts and threads on a schedule from a routine (no Chrome, no splash screens, $0.015–0.20 each), answering @mentions, and Weebo's reads. Keep the browser for replies to other people, likes and follows, which the API forbids. Write posts link-light by default: numbers and story in the text, one link post per day at most, and never put a link in a reply.

Steps for Gocha: in the Developer Console set the app to Read and Write, regenerate keys and tokens, confirm it is inside a Project, set a $20 per-cycle cap and auto-recharge off; then one test post with no link ($0.015) and one with a link ($0.20). If the test returns 403, the forum threads above are the reference and the browser path stays.

Sources

X API pay-per-usage pricing, X API changelog, XDevelopers announcement, April 2026, TechCrunch on the link fee, OpenTweet: pay-per-use explained, OpenTweet: the link fee, SocialNexis: what automation survives, Blotato pricing guide, SocialCrawl, Superframeworks, Gigazine, and the developer forum 403 threads (274069, 274278, 271232).