X on VM0
Read and post from your own X account, without ever handing the agent your password.
Web data · One-time connect · No per-call charge; included in the run
X is the one service here that acts as you. An agent can read profiles, posts, timelines, mentions and recent search, and post when you let it, all from your own account.
That makes control the interesting part. You connect once with your normal X login, VM0 keeps the credential, and the agent never sees it. Reading and posting are separate permissions, so a research agent can watch what is said about you without being able to say anything back.
What X is
Everything else in this catalog answers a question about the world. X is different: it is your account, your timeline and your voice, so the question is not access but control.
Connecting takes one login with your normal X account. There is no X developer account, no key to generate and nothing to paste into a message. VM0 holds the credential and attaches it to the agent's requests on the way out, so a message that tries to talk the agent into revealing it has nothing to reveal.
On top of that sits permission per agent. A research agent gets read-only access and nothing else. Posting is a separate grant, given deliberately, to a specific agent, for as long as you choose.
Most people looking at X API pricing are trying to work out what access costs and how to keep a key out of their code. Here the access is your own account's, so there is nothing extra to buy from VM0, and there is no key in the code to protect because the credential never sits with the agent.
What X can do
What an agent can do with it, and what comes back when it does.
Coverage and limits
What it does not do, said up front, so nobody plans a workflow around something that is out of scope.
Your account's access, not ours
How much you can read, how far back, and how often all follow the X plan your own account has. VM0 makes the connection; it does not buy you a bigger plan.
Recent posts, not the archive
Search covers the recent window X makes available. Digging through years of history needs an X plan that includes the full archive.
Posting is its own permission
Being able to read does not imply being able to post. An agent can only post if you granted that, which is a deliberate act you can undo.
What comes back is not trusted
Posts are public text written by anyone. They are treated as information to read, never as instructions, which stops a reply from steering the agent that read it.
What X costs
Web services are billed in credits per call, not per token. There is no separate vendor bill to reconcile.
curl https://api.x.comThere is no charge on VM0's side. X access comes with the run and counts against your own X account's allowance, so the thing to watch is how much your account is allowed to read rather than a credit balance.
Setup and access
Connect your account once
One login with your normal X account and it is done. No X developer account, no key to generate, nothing pasted into a message. VM0 keeps the credential and attaches it to requests on the way out, so the agent never holds it. That is exactly why an agent can be given access to X without being given your account.
Who can use it
Access is granted per agent, and reading and posting are separate. A research agent can be allowed to read profiles, posts and mentions and nothing more. Posting is a grant of its own, per person and per agent, for as long as you choose, and taking it back leaves everything else untouched.
What teams use X for
Watching what is said about you
A scheduled agent reads mentions and recent posts about your brand, filters out the noise, and surfaces only what a person should answer, with the link, so replying is one click.
Understanding an account before you engage
Before a partnership, a hire or a campaign, pull the profile, the recent posts and what actually got attention, and read a summary instead of scrolling for forty minutes.
Drafting posts you approve
The agent drafts from a report or a launch note and leaves it with you. Because posting is a separate permission, a draft stays a draft until you say otherwise.
When not to use X
Skip it for digging through years of history, which needs an X plan that includes archive search. Skip it for bulk liking, following or replying, which X's own rules do not allow and which gets accounts limited. And do not give a general-purpose agent permission to post for convenience: posting as you is the one thing here that cannot be undone quietly.
What this is called elsewhere
The same thing goes by several names in the market. If you have shopped for one of these, this is how it maps to what you get here.
X API access
Reaching X programmatically rather than through the app. You get that through your own account, which is why your account's plan decides how much you can read and how often.
Twitter API pricing
The question is usually what a tier costs. VM0 adds nothing to it: there is no charge here, and what you can do follows the X plan your own account already has.
Social listening
Watching mentions and recent posts about a brand and surfacing only what someone should answer. This is the reading half of that, on your own account.
Twitter or X automation
Usually means posting on a schedule. It works here, with the important difference that posting is a permission you grant separately, so drafting and publishing are two different decisions.
No API key in your code
The reason this is set up the way it is. VM0 holds the credential and attaches it to requests on the way out, so there is no key sitting in a config file for anything to read.
X compared
X vs keeping an X key in your own code
A key sitting in a config file is readable by anything running there, including a message that talks an agent into printing it. Here the credential is attached on the way out, so the agent never holds it and there is nothing to leak.
X vs an X developer account of your own
You still use your own account's access, but you never register an app, generate keys or rotate them. Connecting is a normal login, which is the difference between five minutes and an afternoon.
X vs reading x.com the hard way
Scraping a logged-out timeline breaks constantly and goes against the terms. This is the real thing, with real fields, acting as an account that is allowed to be there.
The short version
The one service here that uses your own account, and the one where permissions matter most. Connect once, let research agents read, and keep posting as a separate, deliberate grant.
Frequently asked questions
Do I need an X developer account?
No. You connect your normal X account with a single login. There is no app to register and no key to generate.
Where does my credential live?
With VM0, never with the agent. It is attached to requests on the way out, so an agent can use X without being able to read it.
Can the agent post without asking me?
Only if you granted it permission to post. Reading and posting are separate grants, given per agent and revocable on their own.
How far back can it look?
As far as your own X plan allows. Recent posts are covered; the full archive needs a plan that includes it.
Why is X here if everything else needs no account?
Because it acts as you rather than answering a question about the world. It is the one entry that connects, and it still needs no developer account and no key.
Do I need a paid X API plan?
You use whatever access your own X account has. If that is the free level, what an agent can read is limited in the same way; a bigger plan on your account means more here too. VM0 does not sell or resell that access.
What does X access cost on VM0?
Nothing per call. It comes with the run, so the only limit that matters is your own account's allowance.
Is this a Twitter automation tool?
It can post on a schedule if you grant that permission, and it is a poor fit for bulk liking, following or replying, which X's own rules do not allow. The usual pattern is that the agent drafts and you approve.
Is this an alternative to using the X API directly?
It is the X API, reached through your own connected account. What you avoid is registering an app, generating keys, rotating them and keeping them out of your code.
How you ask for X
You describe what you want in plain language. The agent works out which service it needs and makes the calls.
“Check what people said to and about us on X this week and flag only the ones I should answer myself.”
“Look at what @vm0_ai posted this month and tell me which posts got the most engagement and why.”
“Draft three posts from this launch note in our voice and leave them for me to approve.”