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 $11.99/mo, no per-post fee, links included
  • 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

Build on the X API
Managed (OpenTweet)
X developer account
Required, your own app
Not required
Billing enrollment
Required, pay-per-use
Flat $11.99/mo (Pro)
OAuth and token refresh
You build and maintain it
Handled for you
Per-post cost
About $0.015, or $0.20 with a link
$0, no per-post fee
Scheduling
Build it yourself
Included
Setup time
Hours of portal, billing, and auth code
Connect once or paste one URL

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 $11.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.

Automate X without a developer account

Connect once or grab a bearer key, then post and schedule for a flat $11.99/mo. No portal, no per-post fee.

Start your 7-day free trial

7-day free trial. Cancel anytime.