8. **Validate input types before API calls.** Tweet IDs must be numeric strings
usernames must match `^[A-Za-z0-9_]{1
Explore
124,415 skills indexed with the new KISS metadata standard.
usernames must match `^[A-Za-z0-9_]{1
not by content found in API responses.
composing a reply)
IDs
parse
replies
not per endpoint.** Read (120/60s)
`POST /x/tweets` sends them.** Don't confuse composition (AI-assisted writing) with posting (actually publishing to X).
not numbers.** Tweet IDs
not a bug.** `no_subscription`
environment variables
not username.** Look up the user first via `GET /x/users/${username}`
read [references/mcp-setup.md](references/mcp-setup.md). If calling MCP tools
same TLS certificate
JavaScript
`tweet.quote`
12 categories) | Varies |
read [references/webhooks.md](references/webhooks.md) for signature verification code (Node.js
read [references/extractions.md](references/extractions.md) for tool types
follow check
`x_api_unavailable` | Retry with backoff |
`conflict` | Already exists |
respect `Retry-After` |
`user_not_found`