Last updated: July 2026
Do I need an X developer account to automate tweeting?
No, not if you use a managed service that holds the X connection for you. You only need your own X developer app if you build directly against the X API, which now bills pay-per-use with no free tier.
OpenTweet is a Twitter/X scheduler and posting API that holds the X connection for you. Connect your account once, or use an ot_ bearer key, and automate posting without ever opening the X developer portal.
Which path do you need?
There are two ways to automate tweeting. One requires a developer account and pay-per-use billing. The other does not.
Build your own on the X API
- Create an X developer account and register an app
- Enroll the app in pay-per-use billing
- Implement OAuth2 PKCE, store and refresh tokens
- Pay about $0.015 per post, and $0.20 per post with a link
- Build scheduling and rate-limit handling yourself
Use a managed service
- Connect your X account once with OAuth, no dev portal
- Get an ot_ bearer key or a hosted MCP endpoint
- OAuth and token refresh are handled for you
- Flat $19.99/mo, no per-post fee; 1 link post a day on Pro, 10 on Advanced ($29/mo)
- Scheduling is built in
When the developer account is worth it
Build directly on the X API when you need first-party access to something a third party cannot offer, such as full-archive search, or when a first-party integration is a hard requirement. For posting, scheduling, and most automation, the managed path is cheaper and far less setup.Build your own vs managed service
Frequently asked questions
Do I need an X developer account to post or automate tweeting?
No, not if you use a managed service that holds the X connection for you. With OpenTweet you connect your X account once with OAuth, or grab an ot_ bearer key, and never open the X developer portal. You only need your own developer app if you build directly against the X API.
Is the X API still free?
No. Since February 6, 2026 there is no free tier for new API projects. The X API bills pay-per-use: about $0.015 per post, $0.20 per post that contains a link, and about $0.005 per read. You also have to enroll your developer app in billing.
What do I have to set up if I build on the X API directly?
You create an X developer account, register an app, enroll it in pay-per-use billing, implement the OAuth2 Authorization Code with PKCE flow, store and refresh tokens, and handle rate limits and errors yourself. Then you pay per post, including the $0.20 link surcharge.
What does a managed service handle instead?
A managed service like OpenTweet holds the X connection, runs OAuth and token refresh for you, and gives you a single ot_ bearer key or a hosted MCP endpoint. You call one REST endpoint or paste one URL, pay a flat $19.99/mo, and scheduling is included.
When is a developer account actually worth it?
Build directly on the X API if you need first-party access to capabilities a third party cannot offer, such as full-archive search, or if a first-party integration is a hard requirement. For posting, scheduling, and most automation, a managed service is cheaper and far less setup.
Keep exploring
Automate X without a developer account, from your code or an AI agent.
OpenTweet vs the X API
Post, schedule, and automate X without a developer account or the $200/mo minimum.
X DM outreach, human-approved
Find and qualify leads, AI-draft DMs, approve each one, and drip-send from your own account via API or MCP.
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. 44 tools included.
Developer docs
Quickstart, API keys, MCP setup, and the REST reference for posting to X from code or an agent.
Cross-posting reference
One call posts to X, Bluesky and LinkedIn. The platforms field, per-network results, and why a network gets skipped.
Social media API for AI agents
Three ways an agent can post to X, Bluesky and LinkedIn, and the trade-offs of each.
LinkedIn MCP server
Post and schedule to a LinkedIn profile from Claude or Cursor through the official LinkedIn API.
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.
Best MCP servers for social media
The 2026 ranked list. How the hosted OpenTweet MCP compares with the official X MCP and others.
Cheapest way to post to X via code
Flat fee vs pay-per-use. Why the $0.20 per-link fee flips the math past ~145 link posts a month.
X API pricing 2026
Every pay-per-use X API endpoint price from docs.x.com in one searchable table.
Bluesky posting API
Post and schedule to Bluesky with one REST call and OAuth, and cross-post to X and LinkedIn in the same request.
Automate LinkedIn posts
Post to LinkedIn from an AI agent, n8n or a script through the official Posts API, with one REST or MCP call.
Automate X without a developer account
Connect once or grab a bearer key, then post and schedule for a flat $19.99/mo. No portal, no per-post fee.
7-day free trial. Cancel anytime.