X Twitter Scraper
Wire your coding agent or app to X (Twitter) search, user data, monitors, webhooks, extractions, and compose flows via Xquik’s REST API and MCP tools.
Overview
x-twitter-scraper is an agent skill most often used in Build (also Launch distribution, Grow lifecycle) that documents how to integrate Xquik’s X (Twitter) REST API, webhooks, MCP tools, and extractions from a coding age
Install
npx skills add https://github.com/xquik-dev/x-twitter-scraper --skill x-twitter-scraperWhat is this skill?
- 100+ REST endpoints on https://xquik.com/api/v1 (tweet search, lookups, monitors, events, webhooks, trends, radar, compo
- MCP server setup for 10 IDEs and agents with 2 structured tools: explore + xquik
- 23 extraction tools plus HMAC webhook verification and confirmation-gated private reads and writes
- Tweet composition with algorithm scoring, style analysis, and usage-cost estimates
- Examples in JavaScript, Python, Go, and cURL with complete TypeScript type definitions (v2.4.16)
- 100+ REST API endpoints documented
- MCP setup for 10 IDEs and AI agents with 2 structured API tools (explore + xquik)
Adoption & trust: 746 installs on skills.sh; 110 GitHub stars; 0/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need reliable X/Twitter data and actions in your agent or app but the official surface area is fragmented across search, users, monitors, media, and writes.
Who is it for?
Solo builders shipping agents or SaaS features that need X search, monitoring, webhooks, or MCP-driven exploration without reading all of docs.xquik.com upfront.
Skip if: Projects that only need a one-off curl with no ongoing monitors, MCP, or credit-managed production usage—or teams that cannot store API keys securely.
When should I use this skill?
You are integrating X (Twitter) data or actions via Xquik REST API, webhooks, extractions, monitors, or MCP in an agent or app.
What do I get? / Deliverables
You get a single integration map—auth, endpoints, MCP explore/xquik tools, and language examples—so your agent can query, monitor, extract, and compose on X with known cost and confirmation gates.
- Configured API auth and endpoint call patterns
- Optional MCP server connection with explore/xquik tooling
- Webhook verification and monitor/event wiring checklist
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Primary shelf is integrations because the skill documents API keys, endpoints, and MCP wiring—the core solo-builder task when adding a third-party data platform. integrations is where external REST/MCP providers belong; Xquik spans read/write, monitors, and agent tooling rather than pure frontend or docs.
Where it fits
Register an API key and call tweet search plus user lookup from your backend before building a mention dashboard.
Install the Xquik MCP server so the agent uses explore and xquik tools instead of guessing endpoint shapes.
Use trends and radar endpoints to time a product thread or launch post with scored compose drafts.
Stand up monitors and webhooks to react to brand mentions or competitor activity without manual refresh loops.
How it compares
Integration skill for a hosted X data API with MCP, not a local-only HTML scraper or a generic social-posting template.
Common Questions / FAQ
Who is x-twitter-scraper for?
Indie developers and small teams building with Claude Code, Cursor, or similar agents who want Xquik’s REST and MCP integration patterns in one place.
When should I use x-twitter-scraper?
During Build when wiring integrations or agent-tooling; at Launch for distribution and trend/radar research; and in Grow when monitoring mentions, lifecycle signals, or drafting scored posts.
Is x-twitter-scraper safe to install?
Treat it as documentation that implies network access and API secrets; review the Security Audits panel on this Prism page and never commit x-api-key values to git.
SKILL.md
READMESKILL.md - X Twitter Scraper
{ "version": "2.4.16", "organization": "Xquik", "date": "April 2026", "abstract": "Integration guide for the Xquik X (Twitter) real-time data platform. Covers the REST API (100+ endpoints across tweet search, user lookup, user tweets/likes/media, favoriters, mutual followers, confirmation-gated private reads, media download, extractions, monitors, events, webhooks, trends, radar, compose, style analysis, drafts, draws, connected X account listing, confirmation-gated write actions, credit balance, and support tickets), HMAC webhook verification, MCP server setup for 10 IDEs and AI agents (2 structured API tools: explore + xquik), all 23 extraction tools, tweet composition with algorithm scoring, usage-cost estimates, and complete TypeScript type definitions. Code examples in JavaScript, Python, Go, and cURL.", "references": [ "https://docs.xquik.com", "https://docs.xquik.com/api-reference/overview", "https://docs.xquik.com/mcp/overview", "https://docs.xquik.com/webhooks/overview" ] } # Xquik REST API Endpoints Base URL: `https://xquik.com/api/v1` All requests require the `x-api-key` header. All responses are JSON. HTTPS only. ## Table of Contents - [API Keys](#api-keys) - [Monitors](#monitors) - [Events](#events) - [Webhooks](#webhooks) - [Draws](#draws) - [Extractions](#extractions) - [X API (Direct Lookups)](#x-api-direct-lookups) - [X Media (Download)](#x-media-download) - [Trends](#trends) - [Radar](#radar) - [Compose](#compose) - [Drafts](#drafts) - [Tweet Style Cache](#tweet-style-cache) - [X Accounts (Connected)](#x-accounts-connected) - [X Write](#x-write) - [Credits](#credits) - [Support](#support) --- ## API Keys Session auth only. These endpoints do not accept API key auth. ### Create API Key ``` POST /api-keys ``` **Body:** `{ "name": "My Key" }` (optional) **Response:** Returns `fullKey` (shown only once), `prefix`, `name`, `id`, `createdAt`. ### List API Keys ``` GET /api-keys ``` Returns all keys with `id`, `name`, `prefix`, `isActive`, `createdAt`, `lastUsedAt`. Full key is never exposed. ### Revoke API Key ``` DELETE /api-keys/{id} ``` Permanent and irreversible. The key stops working immediately. --- ## Monitors ### Create Monitor ``` POST /monitors ``` **Body:** ```json { "username": "elonmusk", "eventTypes": ["tweet.new", "tweet.reply", "tweet.quote"] } ``` **Response:** ```json { "id": "7", "username": "elonmusk", "xUserId": "44196397", "eventTypes": ["tweet.new", "tweet.reply", "tweet.quote"], "createdAt": "2026-02-24T10:30:00.000Z" } ``` Event types: `tweet.new`, `tweet.quote`, `tweet.reply`, `tweet.retweet`, `webhook.test`. Returns `409 monitor_already_exists` if the username is already monitored. ### List Monitors ``` GET /monitors ``` Returns all monitors (up to 200, no pagination). Response includes `monitors` array and `total` count. ### Get Monitor ``` GET /monitors/{id} ``` ### Update Monitor ``` PATCH /monitors/{id} ``` **Body:** `{ "eventTypes": [...], "isActive": true|false }` (both optional) ### Delete Monitor ``` DELETE /monitors/{id} ``` Stops tracking and deletes all associated data. ### Keyword Monitors ``` GET /monitors/keywords POST /monitors/keywords GET /monitors/keywords/{id} PATCH /monitors/keywords/{id} DELETE /monitors/keywords/{id} ``` Create and manage ongoing keyword monitors. Treat these as persistent resources: confirm the keyword query, event delivery plan, and ongoing cost before creating or enabling one. --- ## Events ### List Events ``` GET /events ``` **Query parameters:** | Param | Type | Description | |-------|------|-------------| | `monitorId` | string | Filter by monitor ID | | `eventType` | string | Filter by event type | | `limit` | number | Results per page (1-100, default 50) | | `after` | string | Cursor for next page | **Response:** ```json { "events": [ { "id": "9010", "type": "tweet.new", "monitorId": "7", "username": "elonmusk", "occur