x_twitter_api

You can search X for posts without official API costs by using a cookie-authenticated Bird GraphQL browsing approach as the primary free retrieval path, falling back to xAI semantic search if needed. This retrieves posts by keyword or handle within a specified date range.

Monitoring Twitter trends and finding ICP signals is done by retrieving normalized X posts with engagement and relevance fields. You can extract recent chatter or reply signals and feed them directly into downstream workflows for tailored outbound outreach.

Getting structured JSON from a social media keyword search involves retrieving items with a consistent schema containing id, text, url, author_handle, date, and engagement metrics. This normalized output supports downstream analysis like trend discovery.

Yes, the x_twitter_api skill supports filtering posts by specific date ranges. You can query recent-window searches for posts by topic or targeted per-handle queries, such as asking the AI to return top matching items from a specific start date to an end date.

Yes, you can use xAI semantic search as a paid fallback for retrieving X posts. The mechanism attempts the free cookie-authenticated Bird GraphQL browser approach first, then automatically switches to the paid semantic search path when the primary method fails.

A key limitation of cookie-based GraphQL for Twitter search is its reliability as a free path, which is why it has a paid xAI semantic search fallback. It requires cookie authentication for browsing and produces normalized outputs that may need downstream processing for EOS research.