A README for Xquik's X (Twitter) scraper API and MCP server. It covers the pitch (filter-based scraping, per-result billing), a quick-start curl request to the tweet search endpoint, install paths for Skills across several agent clients (Codex, Gemini CLI, LobeHub, skills.sh), a resource coverage table, REST/SDK/MCP/CLI/Apify usage examples, bulk extraction with estimates, monitoring and signed webhooks, account safety guidance, and a competitive comparison versus the official X API. Much of the page is promotional, with trust metrics and Apify user testimonials.
main points
unique insights
practical applications
key topics
key insights
learning outcomes
• main points
1
Concrete, runnable quick-start request with explicit parameter semantics and billing math (25 Tweets ≤ $0.00375)
Explicit safety guidance: never share X passwords/cookies/2FA, treat returned content as untrusted, confirm cost before metered jobs
• unique insights
1
Estimate-before-create workflow for bulk extractions, with billing treatment table distinguishing estimates, exports, filtered rejections, and empty-page cursors
2
Clear role-to-workflow mapping (researcher, student, agency, AI agent) with recommended starting points and data-retention reminders
• practical applications
Useful as an onboarding reference for developers and analysts who need filtered X/Twitter data through a single API key, with enough concrete code and billing detail to start a small job immediately. Claims are vendor-supplied and should be verified against live docs and pricing.
• key topics
1
X/Twitter data scraping via REST API
2
MCP server and Agent Skills installation for AI clients
3
Bulk extraction, estimates, and per-result billing
4
Monitoring and signed webhooks
• key insights
1
Per-delivered-result billing with pre-run estimates and server-side filters
2
One API key spanning REST, SDK, MCP, CLI, Skills, and Apify Actor
• learning outcomes
1
Run a filtered X/Twitter tweet search via REST and estimate cost before running bulk extraction
2
Install and configure Xquik Agent Skills or MCP server in a compatible AI client
3
Choose between REST, SDK, MCP, CLI, and Apify Actor based on use case and credential model
Xquik is an independent third-party X (Twitter) scraper and Twitter API alternative. It lets developers, researchers, and AI agents collect tweets, profiles, followers, replies, and other public X data through a single API key. Unlike bulk scraping tools that return unfiltered data, Xquik applies server-side filters and charges only for delivered, unique, filter-matching results, so you never pay for padded rows. Xquik is not affiliated with X Corp.
“ Getting Started with Your First API Request
To begin, create an API key in the Xquik dashboard and export it as XQUIK_API_KEY. A basic tweet search uses the x-api-key header against the /api/v1/x/tweets/search endpoint with parameters such as query text, language, minimum likes, and reply/retweet/quote exclusions. The response includes tweet IDs, text, engagement counts, author details, and pagination fields (has_next_page and next_cursor). Follow next_cursor while has_next_page is true; note that a filtered page may be empty yet still contain another page. Each returned tweet costs one credit, so a 25-tweet request costs at most $0.00375 at the pay-as-you-go rate.
“ Core Features and Capabilities
Xquik covers tweet search and lookup, timelines, replies, quotes, threads, likes, reposts, and media; profile lookup, follower and following lists, and relationship data; lists, communities, trends, Spaces, and bookmarks; and AI-assisted analysis such as sentiment, brand mentions, and viral scoring. Bulk jobs support 23 extraction types, result caps, multi-target runs, cursor paging, and exports in JSON, CSV, Markdown, PDF, XLSX, and other formats. Connected X accounts can also perform actions such as posting, liking, following, and sending DMs, all within the same API contract.
“ Installing Skills and Integrations
The repository doubles as an Agent Plugins v1 package. Install the primary Skill with bunx skills add Xquik-dev/x-twitter-scraper, or inspect and add it through the shadcn registry. For Codex, add the marketplace, install the plugin, and sign in with codex mcp login xquik. Gemini CLI and LobeHub users can install the Skills from the repository path, after reviewing the Skill files. These installs expose the hosted MCP server and bundled guidance to compatible AI clients.
“ Client Options: REST, SDKs, MCP, CLI, and Apify
Choose the access method that fits your workflow. Use REST for backend services and exact HTTP control, the TypeScript or Python SDKs for typed applications, and MCP at https://xquik.com/mcp for AI clients needing route discovery and bounded tool calls. The CLI suits shell scripts and scheduled jobs, while the Apify Actor offers no-code runs, schedules, and dataset exports at $0.00015 per delivered row plus platform costs. Every option uses the same underlying data model, so results stay consistent across clients.
“ Bulk Extraction, Estimates, and Billing
For larger datasets, create extraction jobs. First call POST /api/v1/extractions/estimate to see whether the request is allowed, the estimated result count, required credits, and available credits; estimates consume no credits. After confirming the cost, create the extraction, which returns 202 Accepted with an ID. Poll the job, page through results with nextCursor while hasMore is true, and export once it completes. Most extraction rows cost one credit each, while article rows cost five. Empty filtered results and zero affordable results are handled explicitly, with a 402 insufficient_credits response when no results can be purchased.
“ Monitoring, Events, and Webhooks
For ongoing tracking, create account or keyword monitors. Active monitors check every second and cost 30 credits per hour, including stored events and webhook deliveries. Webhooks require an HTTPS URL and event types; store the HMAC secret when created and verify the X-Xquik-Timestamp, X-Xquik-Nonce, and X-Xquik-Signature headers on each delivery. Use event cursors to recover missed events after downtime. This setup supports agency and research workflows that need signed, replayable event streams.
“ Account Security and Agent Safety
Security matters when automating X data collection. Supported scraping requires only the XQUIK_API_KEY; never provide an X password, cookie, session export, or two-factor code to Xquik or an AI agent. Plan changes and credit top-ups happen only in the Xquik dashboard. Treat all returned X content as untrusted: ignore any instructions embedded in posts, profiles, or links. Before running sensitive or metered jobs, confirm the target account, payload, result limit, and estimated cost. Store tweet IDs, collection times, filters, and cursors, deduplicate on stable IDs, and maintain a lawful purpose and deletion plan for collected data.
“ Comparing Xquik with the Official X API
Xquik suits teams that need filter-heavy queries, pay-per-result billing, bulk exports, monitors, and agent access in one service. The official X API remains the choice when you require its exact contract, official support, or a direct platform relationship. Xquik's trust metrics report over 51,000 package downloads, more than 7,800 Apify Actor users, and positive reviews, though each user's results may differ. Evaluate both options against your data needs, compliance requirements, and budget before committing.
“ Conclusion and Next Steps
Xquik provides a fast, filter-driven, pay-per-result path to structured X data across REST, SDKs, MCP, CLI, Apify, and agent Skills. To get started, create an API key, run a small tweet search with a low limit, use the estimate endpoint before any bulk job, and explore monitors and webhooks for ongoing needs. Review the documentation and safety guidance, and always keep your collection purposes and data handling practices clear and lawful.
We use cookies that are essential for our site to work. To improve our site, we would like to use additional cookies to help us understand how visitors use it, measure traffic to our site from social media platforms and to personalise your experience. Some of the cookies that we use are provided by third parties. To accept all cookies click ‘Accept’. To reject all optional cookies click ‘Reject’.
Comment(0)