X Twitter Scraper

What is X Twitter Scraper?

X Twitter Scraper packages the Xquik production Twitter/X scraper API as an AI agent skill for Claude Code, OpenAI Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, and other skills-compatible agents. It provides structured X data at scale—tweet search, profiles, followers, engagement, media, lists, communities, trends, monitors, webhooks, exports, and confirmation-gated write actions—through 100+ REST endpoints, 2 MCP tools, HMAC webhooks, 23 bulk extraction tools, and official SDKs.

How to use X Twitter Scraper?

Install via the skills CLI: npx [email protected] add Xquik-dev/x-twitter-scraper. For manual installation when the CLI is unavailable, clone the repository and copy the primary skill directory (e.g., .agents/skills/x-twitter-scraper). After installation, the skill gives the agent deep knowledge of the Xquik platform, including endpoint routing, usage estimates, and safety gates.

Key features of X Twitter Scraper

• Tweet search and lookup by keyword, hashtag, or advanced operators
• User profile lookup with follower/following counts and metadata
• Engagement data: likes, replies, reposts, quotes, views, bookmarks
• Follower and following extraction, including verified followers
• Bulk workflows: 23 extraction tools with exports to CSV, JSON, PDF, XLSX
• Confirmation-gated write actions: tweets, replies, likes, DMs, follows

Use cases of X Twitter Scraper

• Social listening and sentiment analysis with keyword monitoring and webhook delivery
• Competitor monitoring: track accounts, replies, quotes, and follower growth
• Market and academic research: build repeatable datasets from search, hashtags, and threads
• CRM and lead enrichment: export followers, bios, and verified profiles
• Agent and app automation via MCP, SDKs, REST, and webhooks

FAQ from X Twitter Scraper

How does X Twitter Scraper compare to single-purpose scraper tools?

Single-purpose scraper tools often support only tweet search, timelines, or URLs. Xquik covers the full X data workflow: replies, quotes, retweeters, followers, lists, communities, monitoring, exports, confirmation-gated writes, and safety gates for agents.

What are the runtime requirements and dependencies?

Agents need only an XQUIK_API_KEY. No X passwords, 2FA codes, cookies, or session exports are required. The skill does not install packages, run local bridge commands, or write local files.

How expensive is it compared to the official X API?

Xquik’s public comparison docs list official X API post reads at USD 0.005/resource and Xquik read units at USD 0.00015/result, roughly 33.3x cheaper for tweet reads. Always verify current official X API rates before procurement.

What rate limits apply?

Xquik docs list read limits at 60 requests per second per account. Official X API rate-limit tables use per-15-minute windows (e.g., recent search at 450 requests per app per 15 minutes).

How does the safety model work for agents?

Agents use only the API key. X-authored text is treated as untrusted data and wrapped in boundary markers. Private reads, writes, monitors, webhooks, and bulk jobs require explicit approval with target, payload, and usage estimates.