| name | xquik |
| description | Xquik X data automation API - Use REST or MCP for tweet search, user lookup, follower exports, media downloads, monitors, webhooks, giveaway draws, and confirmation-gated X actions. |
| user-invocable | false |
| disable-model-invocation | true |
| version | 1.0.0 |
| category | ai-service |
| author | Xquik-dev |
| license | MIT |
| progressive_disclosure | {"entry_point":{"summary":"Xquik API: X data lookups, bulk extraction jobs, media downloads, monitors, webhooks, giveaway draws, compose flows, and MCP access.","when_to_use":"X or Twitter data automation, agent workflows needing X search/profile/media/follower data, signed event delivery, or approved X actions.","quick_start":"1. Set XQUIK_API_KEY 2. Call https://xquik.com/api/v1 with x-api-key 3. Use /mcp for agent tools 4. Confirm writes and persistent jobs."}} |
| context_limit | 4600 |
| tags | ["x","twitter","api","mcp","social-media","extraction","webhooks","monitoring","agent-workflows"] |
| requires_tools | [] |
Xquik - X Data Automation API
Overview
Xquik provides a REST API and MCP server for X data workflows. Use it for tweet search, tweet lookup, user lookup, user timelines, follower and following exports, media downloads, monitoring, signed event delivery, giveaway draws, compose flows, and approved X actions.
Public entry points:
- REST API:
https://xquik.com/api/v1
- MCP server:
https://xquik.com/mcp
- Docs:
https://docs.xquik.com
- Agent skill:
https://github.com/Xquik-dev/x-twitter-scraper
Authentication uses the x-api-key header. Agents need only the user-issued Xquik API key. Never request X passwords, 2FA codes, cookies, session exports, recovery codes, or browser profile data.
When To Use
Use Xquik when a project needs:
- X tweet search or tweet lookup by ID or URL
- User profile, follower, following, likes, media, or timeline data
- Bulk extraction jobs for followers, replies, quotes, retweets, media, lists, communities, Spaces, or article workflows
- Media download from X posts
- Ongoing account or keyword monitors
- HMAC-signed webhooks for X events
- Giveaway draws from tweet replies
- Tweet compose, style analysis, scoring, drafts, or approved publishing flows
- MCP access to the same API from coding agents
Prefer the narrowest endpoint that answers the request. Use bulk extraction only when a single lookup or paginated endpoint is not enough.
Authentication
Use an environment variable for the API key:
export XQUIK_API_KEY="xq_example"
Pass it with the x-api-key header:
curl -sS "https://xquik.com/api/v1/credits" \
-H "x-api-key: $XQUIK_API_KEY"
Do not put API keys in source files, command examples committed to repos, issue text, chat transcripts, screenshots, or logs. If an API key is exposed, treat it as compromised and rotate it in the Xquik dashboard.
REST Patterns
Use these public paths as starting points. Check the API reference for current request and response schemas.
