x-api

Programmatic interaction with X (Twitter) for posting, reading, searching, and analytics. Best for: read-heavy operations, search, public data. Required for: posting tweets, managing account, DMs, and any write flow. Legacy aliases such as X_API_KEY , X_API_SECRET , and X_ACCESS_SECRET may exist in older setups. Prefer the X_CONSUMER_* and X_ACCESS_TOKEN_SECRET names when documenting or wiring new flows. X API rate limits vary by endpoint, auth method, and account tier, and they change over time. Always: Use brand-voice plus content-engine to generate platform-native content, then post via X API: - User wants to post tweets or threads programmatically - Reading timeline, mentions, or user data from X - Searching X for content, trends, or conversations - Building X integrations or bots - Analytics and engagement tracking - User says "post to X", "tweet", "X API", or "Twitter API" - Check the current X developer docs before hardcoding assumptions - Read x-rate-limit-remaining and x-rate-limit-reset headers at runtime - Back off automatically instead of relying on static tables in code - Never hardcode tokens. Use environment variables or .env files.