X (Twitter)

The tenant's own X (Twitter) Developer App API key and secret. Since 2026-03-31 Ayrshare posts to X only with these keys sent on every X-targeting call (X-Twitter-OAuth1-Api-Key / X-Twitter-OAuth1-Api-Secret; Ayrshare does not store them). For posting, SHAI never calls X directly with them - the worker's social tick adds them to the Ayrshare call for a post that names X. Since 2026-10-14 the same keys also read ONE public post's video as a style reference (an app-only bearer token from POST /oauth2/token, then GET /2/tweets/:id with the media expansion, $0.005 a post read); the file is measured and deleted at once. X's API is pay-per-use: no subscription tiers since the legacy Basic (2026-06-01) and Pro (2026-09-01) plans moved to pay-per-use; X's own API has no scheduling endpoint.

connectable today

Connect X (Twitter)

How SHAI connects to it

SHAI talks to it directly, with the key you paste. It is one of the tools SHAI has written up — what it costs, why it matters, what breaks without it — as `x-developer-app` in the tool guide.

What it needs

a key you paste, in Setup or on /connections

Nothing else. It is connectable on this deployment as it stands.

Route read from docs/tools/tools.json (x-developer-app) · verified 2026-09-16 · entry 160 of the integrations list

Whatever a run does with this tool goes through one door and one approval row: reading is allowed by default, anything that writes, sends or spends stops and asks first, and you can set that per tool on Connect My Tools.