Xquik X Data

Use Xquik for X/Twitter search, user lookup, timeline review, monitors, webhooks, and MCP-based agent workflows.

When To Use

• The user asks for public X/Twitter posts, users, timelines, trends, or monitoring.
• The workflow needs REST API calls, webhook delivery, or MCP access to Xquik.
• The task needs a repeatable plan for collecting, filtering, or exporting X/Twitter data.

Public References

• API docs: https://docs.xquik.com/api-reference/overview
• MCP docs: https://docs.xquik.com/mcp/overview
• Source repo: https://github.com/Xquik-dev/x-twitter-scraper

Workflow

1. Clarify the data goal: search terms, account handles or IDs, time window, limits, and output format.
2. Pick the smallest Xquik surface that fits: REST for direct calls, webhooks for delivery, MCP for agent tool access.
3. Confirm the user has an Xquik API key or a configured MCP connection before writing runnable commands.
4. Use the public docs for endpoint names, parameters, and response shapes. Do not invent fields.
5. Keep examples scoped to public data and remove any sensitive user values before saving commands or logs.
6. Summarize results with source URLs, request parameters, and any limits or filters applied.

REST Planning Pattern

• For search tasks, map the user query to the documented search endpoint.
• For user timelines, resolve the user identifier first, then fetch the documented timeline endpoint.
• For repeated collection, define retry, rate limit, pagination, and export handling before running a batch.
• For downstream automation, prefer webhooks when the user needs delivery into another system.

MCP Planning Pattern

• Use MCP when an agent should call Xquik tools directly during a task.
• Point setup work at https://docs.xquik.com/mcp/overview.
• Verify the configured server name, key handling, and available tools before assuming a tool exists.
• Keep the agent prompt explicit about the target account, query, limit, and expected output.

Safety Rules

• Never paste or store API keys, cookies, or account sign-in material.
• Do not claim access to private posts or private account data.
• Do not describe private backend routing or infrastructure.
• Do not fabricate pricing, endpoint names, response fields, or service limits.
• If the docs do not cover a requested action, say it is not confirmed and propose the closest documented option.

Output Shape

When reporting a completed Xquik data task, include:

• Goal and selected Xquik surface.
• Query, account, endpoint family, and filters used.
• Result count or delivery status.
• Any pagination, retry, or export notes.
• Links to the public docs used for setup or implementation.