> ## Documentation Index > Fetch the complete documentation index at: https://docs.hypedexer.com/llms.txt > Use this file to discover all available pages before exploring further. # List prediction questions > Returns prediction questions. Each question groups multiple outcomes (e.g. Akami, Otoro, Canned Tuna) with a fallback outcome. Each question row also reports its provider: `venue` and `deployer` are derived from the question's outcomes (resolved via the fallback outcome's market). Legacy questions report `venue = "oracle"` and `deployer = ""`: see [Permissionless providers and the oracle convention](/hip-4/overview#permissionless-providers-and-the-oracle-convention). ## OpenAPI ````yaml /api-reference/openapi-hip4.json get /hip4/questions openapi: 3.0.3 info: title: 'Hypedexer API: HIP-4 Prediction Markets' version: 1.0.0 description: >- API to query indexed HIP-4 prediction market data on Hyperliquid. HIP-4 introduces on-chain prediction markets (outcome trading). This API indexes: - **Outcomes**: Prediction market outcome definitions with Yes/No sides, volume stats, and question linkage - **Questions**: Groups of related outcomes (e.g. "What will Hypurr eat?" → Akami, Otoro, Canned Tuna) - **Fills**: All executed trades on prediction markets (`#` coins) and outcome spot tokens (`@` coins) - **Providers**: Per-provider trading stats for permissionless venues (plus the legacy `oracle`) - **Deployers**: The permissionless deployer registry (venues, fee scales, delegations) - **Fees**: Aggregated fee breakdown per user, coin, and day - **Settlements**: Market resolution events - **Outcome Tokens**: Spot token metadata for tradeable outcome assets - **Fee Scales**: Governance events for global outcome fee configuration - **User Actions**: On-chain user actions (Split, Merge, Negate outcomes) > ### Permissionless providers Since the permissionless-HIP4 network upgrade (2026-08-29), prediction markets can be deployed by third-party providers (a deployer address operating a named venue), not only by the Hyperliquid oracle. The API attributes every market, question and fill to its provider. Markets with no on-chain venue (pre-upgrade markets, and markets still emitted by the HL oracle pipeline) are reported under the reserved provider name `oracle` in aggregates: see [Permissionless providers and the oracle convention](/hip-4/overview#permissionless-providers-and-the-oracle-convention). ### Fee behavior - `#` prediction market fills currently have `fee = 0` (the `SetOutcomeFeeScale` governance action has not been activated) - `@` outcome token fills (spot) are charged normal spot fees (taker/maker rates) - `fee_usdc` is the fee normalized to USD equivalent ### Pagination All list endpoints support `limit` (default 100, max 10000; `/hip4/providers` and `/hip4/deployers`: max 1000) and `offset` (default 0). ### Time filters - `start` / `end` on fills: epoch **milliseconds** - `start` / `end` on `/hip4/providers`: **ISO datetime** - `start` / `end` on other endpoints: epoch **milliseconds** servers: - url: https://api.hypedexer.com description: Mainnet security: - X-API-Key: [] tags: - name: Analytics description: Time-bucketed prediction market analytics (volume, fills, fees, traders). - name: Providers description: Per-provider trading stats (permissionless venues + the legacy `oracle`). - name: Deployers description: Permissionless deployer registry (venues, fee scales, delegations). - name: Outcomes description: Prediction market outcome definitions and metadata. - name: Questions description: Prediction questions grouping multiple outcomes. - name: Fills description: Prediction market and outcome token fills. - name: Fees description: Aggregated fee analytics. - name: Settlements description: Market resolution events. - name: Outcome Tokens description: Spot token metadata for outcome assets. - name: Fee Scales description: Governance fee scale events. - name: User Actions description: On-chain user outcome actions. paths: /hip4/questions: get: tags: - Questions summary: List prediction questions description: >- Returns prediction questions. Each question groups multiple outcomes (e.g. Akami, Otoro, Canned Tuna) with a fallback outcome. Each question row also reports its provider: `venue` and `deployer` are derived from the question's outcomes (resolved via the fallback outcome's market). Legacy questions report `venue = "oracle"` and `deployer = ""`: see [Permissionless providers and the oracle convention](/hip-4/overview#permissionless-providers-and-the-oracle-convention). operationId: listQuestions parameters: - name: question_id in: query description: Filter by question ID schema: type: integer - name: limit in: query schema: type: integer default: 100 maximum: 10000 - name: offset in: query schema: type: integer default: 0 responses: '200': description: OK content: application/json: schema: type: array items: $ref: '#/components/schemas/Question' example: - question_id: 1 name: What will Hypurr eat the most of in Feb 2026? description: >- Hypurr has committed to weighing and recording daily food intake in a food journal. fallback_outcome: 13 named_outcomes: - 10 - 11 - 12 settled_named_outcomes: [] updated_at: '2026-03-29 23:12:55.370' venue: oracle deployer: '' components: schemas: Question: type: object properties: question_id: type: integer description: Unique question identifier name: type: string description: Question text description: type: string description: Question description / rules fallback_outcome: type: integer description: Fallback outcome ID (e.g. "Other") named_outcomes: type: array items: type: integer description: List of outcome IDs belonging to this question settled_named_outcomes: type: array items: type: integer description: Already settled outcome IDs updated_at: type: string description: Last update timestamp venue: type: string description: >- Provider venue, derived from the question's outcomes (resolved via the fallback outcome's market). `oracle` for legacy questions. deployer: type: string description: >- Deployer address of the venue. Empty string for legacy (`oracle`) questions. securitySchemes: X-API-Key: type: apiKey in: header name: X-API-Key description: 'Include in every request header as `X-API-Key: `.' ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.