Xquik X Data API
Search, extract, and monitor X data through REST, MCP, SDKs, and webhooks.
- Source repo
- Xquik-dev/x-twitter-scraper
- Stars
- ★ 228
- Last updated
- 3d ago
- License
- MIT
- Primary language
- TypeScript
- FA score
- 68/100 · Some gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformCodex · Claude Code
- Cost
- Needs a paid subscription or licence
- Setup effort
- Low · running in minutes
- You'll need
- Typical use
- Researchers running date-, language-, and engagement-bounded Tweet searches while retaining stable IDs, filters, and collection times.
- Not a fit if
- Teams that require fully offline data collection
- Organizations requiring X's official API contract and first-party support
- Projects unwilling to use per-result billing
- Website
- xquik.com ↗ set on GitHub
- Maintenance
- Commits in the last 30 dayslast commit 2026-11-18latest release v2.8.0 (2026-11-05)
- Source review
- 68/100 · Some gaps
What does this agent do, and when should you use it?
Xquik is a third-party hosted API for collecting X (Twitter) data and automating connected accounts; this repository also packages Agent Plugins v1 manifests, Skills, MCP guidance, and client examples. Its coverage includes Tweet search and lookup, profiles, followers, replies, lists, trends, Spaces, bulk extraction, monitoring, and file exports, plus account actions after an X account is connected. Users can access the service through REST, hosted MCP, TypeScript or Python SDKs, a CLI, Apify Actors, and automation integrations. Public reads require an Xquik API key but no official X developer account or connected X account; private reads and account actions require the latter. Results support cursor pagination and delivery as JSON, CSV, Markdown, PDF, TXT, or XLSX, while monitors can produce stored events and signed webhooks. The underlying retrieval runs on Xquik's hosted service, so adoption entails its credit pricing, documented limits, and third-party service boundary.
A client sends filters and an XQUIK_API_KEY to https://xquik.com/api/v1; for example, /x/tweets/search filters Tweets by language, engagement, and content type. The response contains Tweets, authors, and engagement counts, with has_next_page and next_cursor controlling pagination; unavailable optional fields are omitted. For larger jobs, the client first calls POST /api/v1/extractions/estimate to obtain values such as estimatedResults and creditsRequired, then submits the same body to create an extraction, polls it, reads cursor pages, and exports after completion. Monitoring routes such as /api/v1/monitors/keywords watch accounts or queries and deliver updates as stored events or HMAC-signed webhooks. AI clients can connect to https://xquik.com/mcp and use the hosted MCP server's docs, search, and execute tools, while Codex can install the repository's plugin. Application developers can import the XTwitterScraper TypeScript class, and terminal users can invoke the x-twitter-scraper CLI.
- Researchers running date-, language-, and engagement-bounded Tweet searches while retaining stable IDs, filters, and collection times.
- Data teams estimating credits before launching capped, deduplicated bulk extractions with JSON, CSV, or XLSX exports.
- Developers integrating structured X data into Node.js, TypeScript, or Python applications through typed clients.
- Agencies maintaining separate account or keyword monitors per client and receiving replayable, signed webhook events.
- AI-agent users discovering routes through MCP and executing bounded X-data requests with repository-provided Skills.
- Operations teams using a connected X account to post, reply, like, follow, send DMs, or manage supported community actions.
Key setup facts
Pulled from the install and usage notes below. The project README has the current values.
- Install / run
bunx [email protected] add Xquik-dev/x-twitter-scraperbun add x-twitter-scrapergo install 'github.com/Xquik-dev/x-twitter-scraper-cli/cmd/[email protected]'
- Environment variables
XQUIK_API_KEYX_TWITTER_SCRAPER_API_KEY
How do you install or deploy this agent?
REST usage requires no local package. Create an API key in the Xquik dashboard and expose it as an environment variable:
export XQUIK_API_KEY='xq_replace_me'Install the primary Skill in a compatible Agent Plugins v1 client:
bunx [email protected] add Xquik-dev/x-twitter-scraperFor Codex, add the marketplace and install the plugin:
codex plugin marketplace add Xquik-dev/x-twitter-scraper
codex plugin add x-twitter-scraper@x-twitter-scraper
codex plugin listFor the TypeScript SDK:
bun add x-twitter-scraperFor the CLI:
go install 'github.com/Xquik-dev/x-twitter-scraper-cli/cmd/[email protected]'
export X_TWITTER_SCRAPER_API_KEY="${XQUIK_API_KEY}"How do you use this agent?
Make a first REST request with server-side Tweet filters:
curl --get 'https://xquik.com/api/v1/x/tweets/search' \
--header "x-api-key: ${XQUIK_API_KEY}" \
--data-urlencode 'q=machine learning' \
--data-urlencode 'language=en' \
--data-urlencode 'minLikes=100' \
--data-urlencode 'replies=exclude' \
--data-urlencode 'retweets=exclude' \
--data-urlencode 'quotes=exclude' \
--data-urlencode 'limit=25'With the TypeScript SDK, instantiate XTwitterScraper and call client.x.tweets.search:
import XTwitterScraper from "x-twitter-scraper";
const client = new XTwitterScraper({
apiKey: process.env.XQUIK_API_KEY,
});
const page = await client.x.tweets.search({
q: "machine learning",
language: "en",
minLikes: 100,
replies: "exclude",
retweets: "exclude",
quotes: "exclude",
limit: 25,
});The corresponding CLI invocation is:
x-twitter-scraper x:tweets search \
--q 'machine learning' \
--language en \
--min-faves 100 \
--limit 25When processing responses, copy next_cursor unchanged while has_next_page is true and deduplicate on stable Tweet IDs. A filtered page can be empty without ending pagination; bulk exports should wait until the extraction job is complete.
What are this agent's strengths and limitations?
- One service covers Tweets, profiles, social graphs, monitoring, bulk jobs, exports, and connected-account actions rather than isolated lookups.
- Server-side filters, cursor pagination, result caps, and pre-run credit estimates support tightly bounded data work.
- Access paths include REST, hosted MCP, Skills, SDKs, a CLI, Apify Actors, and multiple automation integrations.
- Public reads do not require an official X developer account or connected X account.
- Webhooks support HMAC signatures, nonce and timestamp verification, plus event cursors for recovery.
- Core collection depends on Xquik's hosted service and API key; the repository does not document a self-hosted scraping backend.
- The service consumes credits per delivered result or monitoring hour, and the first PAYG funding amount is $10.
- Private reads and account actions such as posting or sending DMs require a connected X account.
- Deleted, protected, restricted, or unavailable content may remain inaccessible, and optional fields can be omitted.
- Some bounded reply reads can return
424with partial rows and diagnostics; low balances can also stop results early. - The documentation does not yet map every deduplicated row to final credit deductions, so estimates are not final invoices.
How does this agent compare with similar options?
Compared with the official X API, Xquik avoids the need for an official developer account for public reads and emphasizes server-side filtering, per-result billing, bulk exports, monitors, and agent access; the tradeoff is dependence on Xquik credits without X's first-party platform relationship or support. Compared with a general web scraper, it supplies structured records and handles schemas and pagination, but users inherit the vendor's coverage and API boundaries. The Apify Actor suits console runs, schedules, and dataset workflows, although both Actor and platform charges may apply. Building a scraper in-house offers full control over code and storage, while leaving browser state, pacing, proxies, breakage, and maintenance to the adopter.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Xquik X Data API This agent | 68 · Some gaps | Hosted servicePaid | ★ 228 | 3d ago | TypeScript | Codex · Claude Code |
| Bright Data MCP | 62 · Some gaps | MCP serverFreemium | ★ 2.7k | 3d ago | JavaScript | Claude Code · Claude.ai |
| EveryInfra MCP Server & Agent Plugin | 55 · Major gaps | MCP serverPaid | ★ 649 | 1d ago | Python | Codex · Claude Code · OpenAI API |
| webclaw Web Extraction Engine | 80 · Good | CLIFreemium | ★ 2.4k | 2d ago | Rust | Codex · Claude Code · OpenAI API · Claude API |
How does FollowAgents rate this agent?
Why each dimension lost points
The skills restrict credentials to xquik.com, prohibit reusing authenticated headers for returned links, and say not to read OAuth/API keys or handle X login secrets. This supports least privilege and sensitive-data handling, but the product depends on a remote service and the packet gives little detail on retention, processing beyond transmission, or dependency auditing. Private reads, metered bulk jobs, persistent resources, and writes require showing the exact request and obtaining confirmation; write retries are constrained, and monitor pause/delete guidance is included. The materials identify the service as third party and X content as untrusted, but publisher identity is unverified and attribution and maintenance paths are only partly clear.
The README, skills, and MCP manifests describe REST/MCP, cursor handling, authentication, and some failure handling, but contracts differ: the MCP skill specifies OAuth first with an API-key fallback, while the main skill summarizes OAuth/API-key authentication; README and skill pricing statements also do not align fully. Runtime use depends on the hosted Xquik service, with no availability commitment in this packet. The MCP skill gives actionable explanations for 401, 402, 404, 429, dependency failures, and timeouts, so failure guidance is relatively strong.
The skills cover search, profiles, followers, exports, monitoring, analysis, and account actions, while naming exclusions such as other networks and local-only analysis. The main skill has a broad trigger description and the three skills overlap, reducing trigger precision. Setup guidance covers Claude, Codex, Cursor, VS Code and others, with REST, SDK, CLI, and MCP examples, though environment fit still depends on the hosted service and client support.
The repository separates the main, MCP, and research skills and organizes material with references, route tables, examples, and FAQs; the README supplies multilingual installation and connection steps. License and copyright text are complete. Deductions reflect naming variation across x-twitter-scraper, x-developer, and xquik-mcp, a 2.8.0 version without a visible changelog, and maintenance responsibility limited to support, repository, and documentation links without a stated maintenance commitment. Pricing and contract details are marked for rechecking, and some billing semantics are explicitly unresolved.
The skills ask for records, source route, cursor, and applied limits, keep results bounded, and direct large outputs to exports, making results usable for follow-on analysis. MCP route discovery and execution plus REST/API guidance offer practical value. However, value depends on Xquik accounts, quotas, hosted availability, and pricing, while central speed, price, and completeness claims are not independently established by this static packet.
Routes, parameters, response shapes, confirmation rules, error codes, and prices have concrete contracts or examples, and the README gives review dates and source categories. Deductions reflect speed, price, coverage, and usage claims that are publisher assertions or badge/link references which cannot be independently checked from the supplied material, plus partial differences among README, main skill, and MCP/research skill contracts. The skills distinguish user requests from untrusted X content and require stating when embedded instructions are ignored, but marketing claims are not sufficiently separated from verified facts.
- This is a low-confidence static review; no code was executed and the hosted service was not verified. Check the current API contract, pricing, limits, and data-handling terms before use.
- The product sends queries and credentials to the third-party Xquik service; bulk extraction and ongoing monitoring can incur charges. Review estimates, targets, and limits, and confirm before creating them.
- Authentication and pricing descriptions differ across files. Confirm the contract for the specific endpoint when using OAuth/API keys, response billing, or retries.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
Release notes excerpt
Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp. x-developer and its 10 keyword packages are on npm at 2.8.0. What's Changed * Add past trends to the X Trends Scraper README in 9 languages by @kriptoburak in https://github.com/Xquik-dev/x-twitter-scraper/pull/168 * Add spans to the X Trends Scraper README in 9 languages, & Turkish gündem terms by @kriptoburak in https://github.com/Xquik-dev/x-twitter-scraper/pull/169 …View on GitHub ↗ -
Release notes excerpt
Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.View on GitHub ↗ -
Release notes excerpt
Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.View on GitHub ↗
FAQ
Do public X reads require an official developer account or X login credentials?
XQUIK_API_KEY is mandatory. X passwords, cookies, session exports, and 2FA codes must not be sent to Xquik or an agent.How is usage priced?
Does an empty page mean pagination is finished?
has_next_page is true and copy next_cursor exactly rather than decoding or constructing it.Can it post Tweets or send DMs on my behalf?
Can returned data be incomplete?
424 with safe partial rows and diagnostics.Is Xquik X Data API open source?
Is Xquik X Data API safe to use?
Is Xquik X Data API still maintained?
Who makes Xquik X Data API?
What is Xquik X Data API's official website?
Thanks — we use this to improve the page.