Xquik X Data API

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.

1. Researchers running date-, language-, and engagement-bounded Tweet searches while retaining stable IDs, filters, and collection times.
2. Data teams estimating credits before launching capped, deduplicated bulk extractions with JSON, CSV, or XLSX exports.
3. Developers integrating structured X data into Node.js, TypeScript, or Python applications through typed clients.
4. Agencies maintaining separate account or keyword monitors per client and receiving replayable, signed webhook events.
5. AI-agent users discovering routes through MCP and executing bounded X-data requests with repository-provided Skills.
6. Operations teams using a connected X account to post, reply, like, follow, send DMs, or manage supported community actions.

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-scraper

For 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 list

For the TypeScript SDK:

bun add x-twitter-scraper

For 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 25

When 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?

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

How does FollowAgents rate this agent?

FAQ