> ## 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 permissionless deployers > Returns the permissionless deployer registry — one row per deployer/venue, refreshed from chain metadata every ~10 seconds. `sub_deployers` is a JSON **string** the client should parse: an array of `[action, [addresses]]` pairs listing the delegated permissions per venue (e.g. which addresses may `registerQuestionFromTemplate`, `registerStandaloneOutcomeFromTemplate`, `settleOutcome`, `settleQuestion`). The registry covers permissionless venues only; legacy markets have no on-chain venue — 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/deployers openapi: 3.0.3 info: title: HL Indexer — HIP-4 Prediction Markets API 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/deployers: get: tags: - Deployers summary: List permissionless deployers description: >- Returns the permissionless deployer registry — one row per deployer/venue, refreshed from chain metadata every ~10 seconds. `sub_deployers` is a JSON **string** the client should parse: an array of `[action, [addresses]]` pairs listing the delegated permissions per venue (e.g. which addresses may `registerQuestionFromTemplate`, `registerStandaloneOutcomeFromTemplate`, `settleOutcome`, `settleQuestion`). The registry covers permissionless venues only; legacy markets have no on-chain venue — see [Permissionless providers and the oracle convention](/hip-4/overview#permissionless-providers-and-the-oracle-convention). operationId: listDeployers parameters: - name: venue in: query description: Filter by venue name schema: type: string - name: limit in: query schema: type: integer default: 100 maximum: 1000 - name: offset in: query schema: type: integer default: 0 responses: '200': description: OK content: application/json: schema: type: array items: $ref: '#/components/schemas/Deployer' example: - deployer: '0x59900d101574c04a6b8a647feb3db1ab48eb320a' venue: hypurr-markets fee_scale: 1 sub_deployers: >- [["registerQuestionFromTemplate",["0x1733d1945f023dfece04363d26f032ef069accdc"]],["settleOutcome",["0x1733d1945f023dfece04363d26f032ef069accdc"]]] updated_at: '2026-08-29 10:55:41.220' components: schemas: Deployer: type: object properties: deployer: type: string description: Operator address venue: type: string description: Venue name fee_scale: type: number description: Deployer fee scale sub_deployers: type: string description: >- JSON string to parse client-side: array of `[action, [addresses]]` pairs listing delegated permissions per venue (e.g. `registerQuestionFromTemplate`, `registerStandaloneOutcomeFromTemplate`, `settleOutcome`, `settleQuestion`) updated_at: type: string description: >- Last refresh timestamp (registry is refreshed from chain metadata every ~10 s) securitySchemes: X-API-Key: type: apiKey in: header name: X-API-Key description: 'Include in every request header as `X-API-Key: `.' ````