Skip to content
toby
Free trial
Integration · Ready to use

An AI agent that writes and posts on X (Twitter), with your approval

Kai, Toby's X agent, writes posts and threads from what your business actually does: launches, numbers, lessons, your best articles. Connect your own X developer keys and approved posts go out on your account at the time you chose, threads included.

X (Twitter)Ready to use
Access
Your own X developer app keys (Read and Write), for your account only
Publishing
Posts and threads, after your approval, now or at a scheduled time
Cost
The X API is paid per use: X bills you directly. Toby adds nothing.
Setup
About 10 minutes in the X developer portal
Agents
KaiToby

What Toby does with X (Twitter)

Exactly what the connector does today. Reads happen right away; anything that changes, publishes or sends something waits for your approval.

The agents who use it

What you get, concretely

Examples on fictional businesses, in the app's exact format. Numbers are examples, not promises: yours come from your own data.

X (Twitter)

Example

Turn the “how we cut our API latency in half” article into a 6-post thread

Why: Your blog post from the 3rd is your most read of the month, and it has precise numbers (p95 from 480 ms to 210 ms) that perform well on X with a developer audience. It was never shared on X.

Example estimate: one of your three most-viewed posts of the month, and 20–40 visits to the article

First deliverable, ready to paste

1/ We cut Quillbase's API latency from 480 ms to 210 ms (p95). No new servers. Here's what actually worked 🧵
2/ First surprise: 60% of the time was spent serializing JSON we never used. We trimmed responses to the fields clients ask for.
3/ Second: one Postgres index on (workspace_id, updated_at). Biggest win for 3 lines of SQL.
4/ Third: caching auth checks for 30 seconds instead of hitting the database on every call.
5/ What didn't work: a bigger instance. +40% cost, −5% latency.
6/ Full write-up, with the queries: [link to the article]

Kai · X (Twitter)Effort: Low

X (Twitter)

Example

Start a weekly “build in public” post on Fridays

Why: You post on X about once a month, always to announce a feature. Your audience is developers and founders, who follow product numbers and decisions. You already share these figures in your monthly investor update.

Example estimate: a regular presence instead of one-off announcements, about 4 posts a month with no extra writing on your side

First deliverable, ready to paste

Friday post, week 44:
Week 44 at Quillbase
· 1,240 docs sites hosted (+38)
· Shipped: search in code blocks
· Killed: the PDF export nobody used (2% of accounts)
· Learned: people read changelogs when they're 5 lines long
Next week: versioned docs.

Kai · X (Twitter)Effort: Low
KaiScheduled threadExample

Approved, scheduled, published

Content → Thread “API latency”, 6 posts Status: approved by you · scheduled Tuesday 9:00 am Tuesday 9:00 am: published on @quillbase via your X keys Activity log: Published “API latency” via X · link saved on the card: x.com/i/web/status/…
Example for a fictional developer tool. Threads are posted as a chain of replies, each post up to 280 characters.

Connect X (Twitter)

About 10 minutes

An X developer account with an app that has Read and Write permission. The X API is paid per use and billed to you by X.

  1. 1

    Sign in on developer.x.com with the X account you want to post from, and create a project and an app.

  2. 2

    In the app's User authentication settings, set the permission to Read and Write.

  3. 3

    In Keys and tokens, copy the API key and API key secret, then generate the Access token and Access token secret. If you changed permissions after generating them, generate them again.

  4. 4

    In Toby, Integrations → X (Twitter) → Connect, and paste the four keys.

  5. 5

    Approve a first post in Content and click Publish to check everything works.

Good to know

  • The X API is paid. X charges for API usage on its own plans; you pay X directly. Toby does not resell or include X API access.

  • Publishing only. The connector posts and threads; it does not read your mentions, replies, DMs or post analytics.

  • Text posts. Images and videos are not attached through the API yet: add them on X yourself if a post needs one.

  • 280 characters per post. Longer posts are cut at 280, so Kai writes threads when there is more to say.

  • Autopilot is opt-in. By default every post waits for your approval. If you put Kai and your company on Autopilot, he can schedule and publish his own posts, within the caps you set.

Security and trustPricing

Frequently asked questions

Will Toby post on X without asking me?

Not by default. Every post and thread waits for your approval, then goes out when you click Publish or at the time you scheduled. Only if you turn on Autopilot for both Kai and your company can he publish his own posts, and you can pause everything with one button.

Why do I need my own X developer keys?

X requires an API app to post on an account. With your own keys, posts go out on your account without waiting for X to review a shared app, and you keep full control: revoke the keys on developer.x.com and posting stops.

How much does the X API cost?

X sets its API prices and bills you directly, and they change from time to time. Check the current plans on developer.x.com before connecting. A few posts a week is a light use of the API.

Can Kai reply to people or read my mentions?

Not through this connector today: it only posts and threads. Kai can draft replies in chat for you to post yourself.

Does it work with threads?

Yes. Kai writes threads as a list of posts, and Toby publishes them in order, each one as a reply to the previous, so they appear as a single thread.

Can I connect several X accounts?

Each company in Toby connects one set of X keys. If you run a personal account and a company account, the simplest is to connect the account the company should speak from.

Other integrations

Slack & DiscordNotionWordPressAny tool (MCP, API, webhook)All integrations

Use cases and guides

Founders without a marketerSaaSCreators & info productsGrowth Playbook for Community-Led and Repeat-Purchase Brands

Let Kai write your next X thread

Create your account, paste your URL and get your growth audit, your Brand Brain and your first three recommendations, already prepared.

Start free trial

7-day free trial, then $99/month per company. Cancel anytime. Already have an account? Sign in