Monitor an X account

Monitor an X account

Creates a monitor that checks one X account every second and records the event types you choose, such as new posts, replies, quotes and profile changes.

Note: Needs 30 available credits, then bills 30 credits an hour while active; pause it with PATCH /monitors/{id} and isActive false. Read events with GET /events or send them to a webhook from POST /webhooks. An API key needs the monitors scope.

Set up

Use the first option your agent supports.

MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "xquik": { "url": "https://xquik.com/mcp?codemode=false" } } }

Call the MCP tool createMonitor.

Server URL: https://xquik.com/mcp?codemode=false

Note: Native mode: one tool per API operation, named by its OpenAPI operationId. The plain https://xquik.com/mcp is Code Mode, with only docs, search, execute and whoami. Tools list before sign-in; the first tool call starts the OAuth sign-in.

CLI (official)

Install the command, then confirm it runs.

go install github.com/Xquik-dev/x-twitter-scraper-cli/cmd/x-twitter-scraper@latest
x-twitter-scraper --version

Run x-twitter-scraper monitors create.

Set $X_TWITTER_SCRAPER_API_KEY in your environment first (get a key: https://dashboard.xquik.com/en/api-keys).

Note: Needs Go, with $(go env GOPATH)/bin on PATH. The variable holds the same xq_ key the REST API takes.

API (official)

• Base URL: https://xquik.com/api/v1
• Endpoint: POST /monitors
• Auth: send the header x-api-key: $XQUIK_API_KEY
• Get a key: https://dashboard.xquik.com/en/api-keys
• Docs: https://docs.xquik.com/api-reference/overview

Note: Public reads need no X account; posting, DMs and private reads need one connected in the dashboard. Calls spend credits and a 402 means the balance is too low. A key always has the read scope; monitors and writes need their scopes added on the key.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

Rules

• Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
• Never print API keys.