Give your AI agent the keys to grow on X.
ClimbX already drafts in your voice, reads what works at your size, and ships posts for you. Now your own agent can do it over a simple REST API. Publish, schedule, and read your real analytics and voice profile. No scraping, no browser automation, no fragile glue.
Included with any paid plan or trial. No extra add-on.
What your agent can do
One call ships a post to X through the owner’s connected account. Same link-block and quality gates as the app.
Queue posts for any future time. The existing publish pipeline ships them at the minute, retries on failure.
Pull per-post metrics and a format breakdown so your agent reasons about what is working before it drafts.
Fetch the owner’s voice profile and evidence-backed learnings so drafts sound like them, not like a bot.
Built with the same guardrails as the app
- No link posts. URLs in a post cut reach by 50 to 90% and cost 13x to publish, so the API rejects them - the same rule the composer enforces.
- A daily cap. Posting is capped at 5 posts per day per account while the API is young. Enough to run a real cadence, low enough to keep a runaway loop from flooding your feed.
- Your account, your control. Keys are scoped to one ClimbX account, shown once, and revocable instantly. Revoke a key and anything using it stops on the next call.
For builders running their own agents
If you are wiring up an autonomous setup - openclaw, hermes, or your own stack - ClimbX is the growth layer. Your agent handles the reasoning; ClimbX handles the X-specific parts that are tedious to get right: what works at your size, drafting in your voice, and shipping on a schedule that respects the algorithm. Start with the API. MCP lands if the demand is there.
Frequently asked questions
What can the ClimbX API do?
Three things, one REST call each: publish a post to X through your connected account, schedule a post for any future time, and read your real analytics and voice profile so your agent knows what is working before it drafts.
Does ClimbX use browser automation or scraping?
No. The API publishes through a real server-side endpoint, not a headless browser or a scraper. That is the point: you replace brittle automation that breaks when a page changes with a stable publishing API.
Is there a free tier?
No. ClimbX is paid-only with a 7-day trial that requires a card. The API is included with any paid plan or the trial at no extra cost - there is no separate API add-on to buy.
Can my agent post links?
No. URLs are rejected at the API, the same rule the app enforces. A link in a post cuts reach by 50 to 90% and costs 13x more to publish. Post the thought through the API, then drop the link in a reply yourself.
How many posts can the API send per day?
Five per account per day while the API is young. Enough to run a real cadence, low enough that a runaway loop cannot flood your feed. We raise it as we watch how the API gets used.
How does authentication work?
Bearer keys. Create a key in ClimbX, scoped to one account and shown once, then send it as an Authorization header. Keys are stored only as a hash and revocable instantly - revoke one and anything using it stops on the next call.
Do you support MCP?
Not yet. We are starting with a plain REST API because it is the lowest-friction way for people already building agents to plug in today. MCP is a natural next step and we will ship it if the demand is there.
Ready to grow on X?
7-day trial. Cancel anytime. Limited to the first 100 founding members.
0 founding spots left.
Early testing. Payments are not yet active. Interested? Email [email protected] or DM @DanielSmidstrup on X.