Post to X from an
ElizaOS agent
Skip the X developer account and the OAuth secrets in your character file. Use OpenTweet as your agent's posting backend and it ships to X with a single bearer key.
7-day free trial. No X developer account needed.
What your agent can do on X
A posting layer for autonomous and on-chain agents that live on X.
Post now
Your character publishes a tweet with a single API call.
Schedule
Queue market updates or recaps for set times.
Threads
Turn a longer analysis into a connected thread.
Media
Attach charts and images or generate them with OpenTweet.
Multi account
Run several agent personas across separate X accounts.
No X API keys
No developer account or OAuth secrets in your character file.
One call replaces the X API setup
Have your agent POST to the OpenTweet API instead of wiring raw X credentials into your character. No developer account, no OAuth handshake.
// Post to X from your ElizaOS agent via OpenTweet
// One bearer key, no X developer account, no OAuth secrets
await fetch("https://opentweet.io/api/v1/posts", {
method: "POST",
headers: {
"Authorization": "Bearer ot_your_api_key",
"Content-Type": "application/json",
},
body: JSON.stringify({
text: "gm. on-chain volume is up 18% today.",
publish_now: true,
}),
});Want the full toolset for an MCP-aware agent? Use the OpenTweet MCP server.
Perfect for
On-chain market agents
Solana and EVM agents that post market commentary and sentiment to X around the clock.
Autonomous personas
Character agents that hold their own X presence and post in their own voice.
Project update bots
Agents that announce releases, proposals, and metrics for a token or protocol.
Non-developer builders
Ship a posting agent without applying for X API access or writing OAuth code.
Frequently asked questions
How do I make an ElizaOS agent post to Twitter?
Instead of wiring the native Twitter plugin to raw X API credentials, have your agent call the OpenTweet API to publish. It is a single HTTP POST with a bearer key, so your character posts without an X developer account.
Why not just use the ElizaOS Twitter plugin directly?
The native plugin requires a full X developer account, API keys, and OAuth setup in your character config, which is the most common blocker for non-developer crypto builders. OpenTweet replaces all of that with one key.
Is this good for Solana and other on-chain agents?
Yes. Many on-chain agents built on ElizaOS use X as their main output channel for market commentary and updates. OpenTweet gives them a reliable posting layer without touching X API billing.
Can the agent schedule posts and threads?
Yes. The OpenTweet API accepts scheduled times, thread arrays, and media, so your agent can queue posts or publish threads, not just single tweets.
What does it cost?
OpenTweet is a flat $11.99/month and absorbs the underlying X posting cost at normal volumes. There is no per-post fee and no link-post surcharge, unlike the pay-per-use X API.
Wire any agent or framework to X
ElizaOS is one of many. Post to X from code, an MCP client, or any AI agent.
OpenTweet vs the X API
Post, schedule, and automate X without a developer account or the $200/mo minimum.
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. 30 tools included.
An MCP server that posts to X
X's official MCP server is read-only. Here is one that actually posts, schedules, and threads.
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.
Give your agent an X account it can run
Connect X, copy your key, and let your ElizaOS agent post today.
Start your 7-day free trial