Pick the agent interface
Docs MCP
Use
https://docs.xquik.com/mcp for public docs, API reference pages,
examples, troubleshooting, or type definitions. It is read-only and requires
no auth.API MCP
Use API MCP at
https://xquik.com/mcp for live calls. Full account
keys and OAuth tokens expose every catalog route. Guest paid_reads keys
expose only the eligible GET routes. Current SDKs negotiate MCP
2026-07-28 through server/discover.REST or SDK
Use REST or generated SDKs when a service owns work outside the chat
session. That means retries, cursor storage, file downloads, queues,
or batch jobs.
Webhooks and replay
Use monitor webhooks for fresh events. Use
GET /api/v1/events when a
receiver, queue, warehouse, or agent run needs replay.Use the default agent route
- Search public docs or
llms.txtbefore requesting current API data. - Use
docsfor product guidance. Usesearchbeforexquik.request(...). That search confirms the endpoint path, required parameters, costs, and response shape. - Keep requested filters. Never add others. Call
xquik.request({ path, method?, query?, body? })with the smallest useful page. Hosted MCP injects authentication and required idempotency headers. - Continue while
has_moreis true andnext_cursoradvances. - Return normalized rows, IDs, counts, samples, and cursors instead of full raw pages.
- Hand long-running or replayable work to REST, SDKs, webhooks, or exports.
402 creates no checkout, and its MCP answer names no checkout step. Report the balance, the required credits and the dashboard link. The user adds credits at that link in the browser. MCP has no checkout, top-up, subscription or guest wallet tool.Route guest paid reads
An active guest key givessearch and execute a read-only catalog. It lists the eligible operations. The docs tool remains available. Every route appears in the guest paid-read inventory. Batch GET /api/v1/x/tweets reads every tweet ID the URL holds.
The sandbox cannot execute writes, account actions, automations, billing, or credential management. It cannot execute any other read either. OAuth and full account behavior remain unchanged.
If the guest key needs creation, activation status, or more credits, leave MCP. Then follow the accountless guest wallet flow through direct REST.Creation and top-up require explicit user confirmation. Status polling does not create payment.
Never place the guest key in tool code, chat output, or shared agent state. Never place its creation Idempotency-Key there either.Return stored rows
MCP returns normalized snake_case fields, structured errors, and date-time fields as Unix seconds. Keep agents onhas_more and next_cursor. Do so even when REST or SDK pages show camelCase response fields. Read a REST createdAt field as created in MCP results.Follow cursor rules
Full account sessions can check
GET /api/v1/credits before large reads.
Guest sessions receive balance and top-up context in 402. The direct
REST guest status route reports the balance. Low balances can return
smaller pages. Zero affordable rows can return 402 insufficient_credits.
Follow these rules for high-volume MCP reads.- Deduplicate tweet or user rows by stable
id - Continue through empty pages when
has_moreis true - Stop at the requested total, page cap,
has_more: false, orcursor_stalledwhen cursors repeat. Keep output below 24,000 characters.
Store handoff state
Store the values a later agent, service, or workflow needs. Then it can resume without reading chat history.Know when to leave MCP
File exports
Use extraction export endpoints for CSV, JSON, XLSX, Markdown, or PDF files.
Webhook receivers
Use signed webhooks when downstream systems need fresh monitor events.
Replay jobs
Use stored events and delivery rows when receivers miss work.
SDK backends
Use SDKs when a backend owns retries, storage, and batch orchestration.
Continue with focused references
MCP tools reference
Review Code Mode, OpenAPI-native tools, response contracts, and examples.
Docs MCP server
Connect read-only documentation search beside the API MCP server.
No-code handoff
Hand monitor events, exports, and direct reads to workflow platforms.
Webhook testing
Verify signed receivers before accepting production events.