Live Xquik tool: search the 120-route API catalog before calling 'xquik'. This package stub returns setup guidance only.

When to use

• Use 'explore' FIRST to find the right endpoint path, parameters, and response shape before calling 'xquik'.

• Use when the user asks what capabilities are available or how to accomplish a task on X/Twitter.

• Use to check whether an endpoint is included usage or requires account access.

When NOT to use

• Do NOT use 'explore' to fetch live data from X - use 'xquik' instead.

• Do NOT use if you already know the endpoint path and parameters.

Behavior

• Live server: read-only, idempotent catalog search with no API request.

• Package stub: makes no network call and returns live setup guidance.

• The live catalog has 120 routes. Of these, 119 support JSON or text.

• Each EndpointInfo contains method, path, summary, category, free, parameters, and responseShape fields.

Input format

Provide a bounded request function. The server exposes spec.endpoints (EndpointInfo[]). Filter, search, or return them.

Examples

Find all included-usage endpoints: async () => spec.endpoints.filter(e => e.free) Find by category: async () => spec.endpoints.filter(e => e.category === 'composition') Search by keyword: async () => spec.endpoints.filter(e => e.summary.toLowerCase().includes('tweet')) Get full details: async () => spec.endpoints.find(e => e.path === '/api/v1/x/tweets/search')

Live Xquik tool: send confirmed requests across 120 catalog routes. This package stub returns setup guidance only.

When to use

• Use after calling 'explore' to discover the endpoint path and parameters.

• Use for live X/Twitter operations such as tweet search, user lookup, giveaway draws, extraction jobs, composition, private reads, persistent monitors, webhooks, and confirmation-gated writes.

• Confirm private reads, persistent resources, metered operations, and writes before using endpoints that require user approval.

When NOT to use

• Do NOT use to discover endpoints - use 'explore' first.

• Do NOT pass API keys or auth headers - authentication is injected automatically.

Behavior

• Live server: processes xquik.request(path, options?) inside a bounded sandbox.

• Package stub: makes no API request and returns live setup guidance.

• The live tool has no filesystem or arbitrary network access.

• 119 catalog routes support JSON or text. Binary support downloads use REST.

• Mutating operations require prior user confirmation and can return durable actions.

• Pagination responses include has_more and next_cursor. Pass cursor for the next page.

• Some operations modify X or Xquik resources. Show the exact payload, target, and usage estimate before calling them.

Error handling

• 402: Account access or usage balance requires dashboard attention. Explain the account state and direct the user to the dashboard before retrying.

• 429: Rate limited. Retry after backoff.

• 404: Resource not found, such as a missing user, tweet, or monitor.

• Durable writes: follow safe_to_retry and next_action before retrying.

Input format

Provide a bounded request function using xquik.request(path, { method?, body?, query? }). Auth is automatic.

Examples

Search tweets: async () => xquik.request('/api/v1/x/tweets/search', { query: { q: 'AI agents', limit: '50' } }) Get user: async () => xquik.request('/api/v1/x/users/elonmusk') After explicit user confirmation, post tweet: async () => xquik.request('/api/v1/x/tweets', { method: 'POST', body: { account: '<confirmed_account>', text: '<confirmed_text>' } })