Skip to main content
HTTP API connector An HTTP API described by an OpenAPI spec, not an MCP server. Calls go to https://api.twitter.com/2 and carry a credential xpander supplies, so there is nothing to paste.

​
What the skill can do

API connector: 4 actions, as they appear in the skill panel. 0 of them create, change or delete something in X; mark those under These actions need approval when you add the skill to an agent.
  • Post service (4): Search Recent Tweets, Look Up User by Username, Get User’s Tweets, Get Tweet by ID

​
Connect X

In Xpander Chat, open the agent’s settings, click Add skill, and search for X. The connect dialog asks for a connection name and whether the connection is for the Organization (one shared account) or Personal (your own account, so the agent acts with your permissions where systems allow). On an agent other people use, a personal connection runs their requests as you unless the binding requires each person’s own sign-in; see whose credential a shared agent uses. X connects with Sign in with X: you authorize in the browser and xpander stores the OAuth token; the agent never sees it, and the token is attached at the moment a skill is called. Calls go to https://api.twitter.com/2.

​
Give an agent the X skill

Once X is connected, any agent you can edit may be given the skill: open the agent’s settings, click Add skill, and choose X. Enable only the action groups the agent needs, and mark the actions that should wait for a named person’s sign-off under These actions need approval. Which skills exist for your organization, and who may add them, is decided by your admins; see Skills.