> ## 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 outcomes > Returns prediction outcome definitions with volume stats. Each outcome (e.g. "Canned Tuna") has Yes/No sides and may belong to a question. Use `question_id` to get all outcomes for a question. Since the permissionless-HIP4 upgrade, every market row carries `venue`, `deployer` and `deployer_fee_scale` attributing it to its provider. Oracle-emitted (legacy) markets have `venue = ""`, `deployer = ""` and `deployer_fee_scale = 0`: see [Permissionless providers and the oracle convention](/hip-4/overview#permissionless-providers-and-the-oracle-convention). Also available as `/hip4/markets` (alias). ## OpenAPI ````yaml /api-reference/openapi-hip4.json get /hip4/outcomes 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/outcomes: get: tags: - Outcomes summary: List prediction outcomes description: >- Returns prediction outcome definitions with volume stats. Each outcome (e.g. "Canned Tuna") has Yes/No sides and may belong to a question. Use `question_id` to get all outcomes for a question. Since the permissionless-HIP4 upgrade, every market row carries `venue`, `deployer` and `deployer_fee_scale` attributing it to its provider. Oracle-emitted (legacy) markets have `venue = ""`, `deployer = ""` and `deployer_fee_scale = 0`: see [Permissionless providers and the oracle convention](/hip-4/overview#permissionless-providers-and-the-oracle-convention). Also available as `/hip4/markets` (alias). operationId: listOutcomes parameters: - name: outcome_id in: query description: Filter by outcome ID schema: type: integer - name: question_id in: query description: 'Filter by question ID: returns all outcomes for that question' schema: type: integer - name: class in: query description: Filter by class (e.g. `priceBinary`) schema: type: string - name: underlying in: query description: Filter by underlying asset (e.g. `BTC`, `HYPE`) schema: type: string - 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/Outcome' example: - outcome_id: 11 coin: '#11' name: Canned Tuna description: Affordable tuna for bear markets class: '' underlying: '' expiry: '' target_price: 0 period: '' side_specs: '[{"name":"Yes"},{"name":"No"}]' question_id: 1 quote_token: 0 block_time: '2026-03-29 23:12:55.308000000' question_name: What will Hypurr eat the most of in Feb 2026? question_description: >- Hypurr has committed to weighing and recording daily food intake in a food journal. total_fills: 2 total_volume: 21.4 unique_users: 2 venue: '' deployer: '' deployer_fee_scale: 0 - outcome_id: 31207 coin: '#31207' name: HYPE above 100 on Sep 30? description: Settles to Yes if HYPE trades above 100 on 2026-09-30. class: '' underlying: '' expiry: '' target_price: 0 period: '' side_specs: '[{"name":"Yes"},{"name":"No"}]' question_id: null quote_token: 0 block_time: '2026-08-29 09:14:02.114000000' question_name: '' question_description: '' total_fills: 152 total_volume: 8412.7 unique_users: 37 venue: hypurr-markets deployer: '0x59900d101574c04a6b8a647feb3db1ab48eb320a' deployer_fee_scale: 1 components: schemas: Outcome: type: object properties: outcome_id: type: integer description: Unique outcome identifier coin: type: string description: Prediction market coin (e.g. `#11`) name: type: string description: Outcome name (e.g. `Canned Tuna`, `Recurring`) description: type: string description: Outcome description or structured metadata for priceBinary class: type: string description: Market class (e.g. `priceBinary`). Empty for custom outcomes. underlying: type: string description: Underlying asset (e.g. `BTC`, `HYPE`). Empty for custom outcomes. expiry: type: string description: Expiry datetime (e.g. `20260329-0500`) target_price: type: number description: Target price for priceBinary outcomes period: type: string description: Period (e.g. `15m`, `1d`) side_specs: type: string description: JSON array of side names (e.g. `[{"name":"Yes"},{"name":"No"}]`) question_id: type: integer nullable: true description: Parent question ID (null if standalone) quote_token: type: integer description: Quote token index block_time: type: string description: Creation timestamp question_name: type: string description: Parent question name (empty if no question) question_description: type: string description: Parent question description total_fills: type: integer description: Total number of fills on this outcome total_volume: type: number description: Total traded volume in USD (sum of px * sz) unique_users: type: integer description: Number of unique users who traded this outcome venue: type: string description: >- Provider venue name. Empty string for oracle-emitted (legacy) markets: see the oracle convention. deployer: type: string description: >- Deployer address operating the venue. Empty string when `venue` is empty. deployer_fee_scale: type: number description: Deployer fee scale for this market. `0` when not applicable. 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.