social · wired today
Twitter/X, wired into your agent workforce
External systems are where agent answers come from. The Twitter/X connector is one of 205 executable connectors and gives agents 5 tools, with the credential held in the vault and every call receipted.
Connecting Twitter/X takes one credential
You provide API key, API secret, access token, access secret from your Twitter/X account. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Twitter/X's own API documentation ↗ covers creating and scoping the credential.
What agents can run against Twitter/X
verify_credentialsVerify the connected Twitter/X credentials and return the authenticated account (id, username, name).
get_tweetRead a single X (Twitter) post by id, including public metrics (likes/retweets/replies) and creation time. Reads cost pay-per-use credits on X's API (roughly $0.005 each) — do not loop this casually; a single lookup answers "what does this post say / how is it performing".
get_user_tweetsRead recent posts from an X (Twitter) user's timeline (max 20 per call). Omit user_id to read the CONNECTED account's own timeline. Reads cost pay-per-use credits on X's API (roughly $0.005 each) — do not loop this casually to build a large history; use a single call with the max_results you actually need.
search_recentSearch recent X (Twitter) posts (last ~7 days) matching a query, max 20 results per call. Reads cost pay-per-use credits on X's API (roughly $0.005 each) — do not loop this casually across many queries; use X search operators in a single well-formed query where possible.
get_mentionsRead recent mentions of the CONNECTED X (Twitter) account, optionally only those newer than since_id. Reads cost pay-per-use credits on X's API (roughly $0.005 each) — do not loop this casually; the inbound mention poller already calls this on a schedule for HITL inbox items, so an agent typically only needs this for an on-demand check.
How proven is this?
The Twitter/X connector is a hand-written module that has been exercised against the live Twitter/X API.
Twitter/X integration FAQ
What can Quox agents do with Twitter/X?
Agents can run 5 tools against Twitter/X: verify credentials, get tweet, get user tweets, search recent, get mentions. Every call is receipted in the evidence trail.
What does the Twitter/X integration need?
You provide API key, API secret, access token, access secret from your Twitter/X account. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Twitter/X credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Twitter/X connector?
The Twitter/X connector is a hand-written module that has been exercised against the live Twitter/X API.