Connect X (Twitter) to your AI agent
Tweets, users & search.
What it changes
An agent that can read your channel can answer about content it has actually seen, and pull the clip somebody is asking about.
What people ask once it is connected
How to connect it
- 1
Paste your access token
Generate a token in the provider’s settings and paste it in. Scope it to the least it needs — read-only where reading is all the agent does.
Stored as
X_BEARER_TOKEN - 2
The agent is briefed automatically
Connecting it hands the agent a short description of what X (Twitter) provides and how to call it. You write no routing rules and no prompts.
Social. GET /tweets/search/recent?query=QUERY with Bearer token. - 3
Ask it something that needs live data
The agent decides a request is needed, makes it, and answers with what came back. If the call fails it says so rather than filling the gap with a guess.
The technical details
- Base URL
- https://api.twitter.com/2
- Authentication
- Access token
- Secret name
- X_BEARER_TOKEN
- Category
- Social
Your key or ours. On your own key, calls run against your account and spend no credits. Where we offer a managed key for a connector you can use ours instead and pay per request in credits — priced per connector, refunded when a request fails.
Questions
What can my AI agent do with X (Twitter)?
Tweets, users & search. Posts, videos, comments and audience data from social platforms. The agent calls it during a conversation, when the answer needs live data rather than a stored one.
Do I need my own X (Twitter) key?
Either. Paste your own X_BEARER_TOKEN and calls run on your account with no credits spent. Where we offer a managed key for a connector, you can use ours instead and pay per request in credits.
Where is my key stored?
Sealed, write-only. It is encrypted before it is written, never returned to any browser — including yours — and only ever sent to the provider it belongs to. You can replace or remove it at any time.
How does the agent know when to use it?
Connecting it adds a short brief to the agent describing what X (Twitter) provides and how to request it. The agent reads that and calls it when a question needs it — you do not write any routing rules.
What if X (Twitter) is down or the key is wrong?
The agent says so and carries on with what it does know, rather than inventing an answer. A failed managed request is refunded.
Give your agent live data
Describe what you do in a sentence, then connect X (Twitter) in the agent’s Connectors tab. It starts using it in the next message.
Build your agent free