explore
Find the right endpoint for your X/Twitter task by searching the API catalog. Filter by category, keyword, or free usage to identify parameters and response shapes.
Instructions
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')
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | Bounded request function that filters or searches spec.endpoints (EndpointInfo[]). Must return an array or single EndpointInfo object. Example: async () => spec.endpoints.filter(e => e.category === 'twitter') |