Skip to main content
Quick reference for terminology used throughout the Xquik platform and API.

​
Core concepts

A persistent watcher on an X user that streams events via webhooks. Monitors run continuously and detect changes like new tweets, follower gains, and profile updates. Each subscription includes 1 monitor; additional monitors are $5/month each.
A batch job that pulls historical data (tweets, followers, etc.) into exportable results. Extractions are metered operations — credit cost depends on the volume of data returned.
A giveaway selection tool that picks winners from extraction results. Draws support filters (minimum followers, account age) and produce a transparent, publicly verifiable result page.
A change detected by a monitor (new tweet, follower gained, profile update, etc.). Events are delivered to your server via webhooks or integrations in real time.

​
Billing & usage

The metered unit for API usage. Each operation costs 1-10 credits depending on the endpoint. Credits are included in your subscription and reset each billing period.
Operations that deduct credits from your balance. Includes reads, writes, and extractions. When credits are exhausted, metered calls return 402 Payment Required.
Operations that are free and do not consume credits. Includes monitors, webhooks, integrations, and account management endpoints.
Pay-as-you-go — credit-based usage within a subscription. Extra usage beyond the included allowance is billed at a per-credit rate.
Machine Payments Protocol — pay-per-call with USDC, no subscription required. Designed for autonomous agents that pay for each API call individually.

​
Delivery & integrations

An HTTP callback that delivers real-time monitor events to your server. Webhooks use HMAC-SHA256 signatures for payload verification. See the webhook guide for setup details.
A third-party connection (Discord, Telegram, Slack) that forwards monitor events. Integrations provide a no-code alternative to webhooks for receiving real-time notifications.
An operation that modifies X state — tweet, like, follow, DM, etc. Write actions cost 10 credits and require a connected X account.

​
API & technical

Authentication credential passed via the x-api-key header. Generate keys from the dashboard or the API keys endpoint.
A pagination method using opaque cursor tokens instead of page numbers. Pass the cursor value from the previous response to fetch the next page. More reliable than offset-based pagination for real-time data.
The rate-limiting algorithm used by Xquik. Each user account gets a counter per tier (read, write, delete) that resets every 60 seconds. Requests are rejected with 429 when the counter exceeds the tier limit. See rate limits for details.