outcomeMeta
Returns currently active outcomes with their descriptions and side specifications.
Integrate Hyperliquid prediction markets using the leading tech stack, trusted by 80+ teams.
We provide the best dev experience for teams integrating HIP-4. Convenient API schema, direct connection to founders, and quick implementation of feature requests. Hydromancer is built for ambitious teams.
HIP-4 lets teams deploy outcome markets, contracts in the style of prediction markets and binary options. Price discovery happens through CLOB, akin to spot markets on Hyperliquid.
The core difference between Polymarket, Kalshi, and Hyperliquid is that outcome markets are builder-deployed. Any team staking enough HYPE can deploy outcome markets, similar to perp markets deployed using HIP-3.
An outcome is a single market with one or more sides, typically Yes / No. A question groups outcomes together with a fallbackOutcome. At expiry, each outcome resolves to a settleFraction between 0 and 1.
Hydromancer is the data layer: we index every registered outcome, surface settlement the moment it lands, provide analytics, and expose all of it through the full HIP-4 endpoint surface.
Query active outcomes, registered markets, enriched stats, settlement data, and resolution history through one production API.
Returns currently active outcomes with their descriptions and side specifications.
Recently registered, unsettled outcomes, newest first. Filter by class, underlying, or period. Perfect for new market feeds.
Returns metadata and stats for one or more registered prediction market outcomes that have not yet been settled.
Recently settled outcomes, newest first. Filter by class, underlying, period, or name. Powers history feeds and resolution timelines.
Returns metadata and enriched stats for one or more settled prediction market outcomes, including first trade, largest trade, vWAP, unique traders, and more.
Our HIP-4 endpoints share auth, shape, and infrastructure with our core Hyperliquid DEX and HIP-3 stack. Integrate once and get the whole Hyperliquid data surface with it.
Perps, spot, L2/L4 orderbook, fills, liquidations, and user state.
Every deployer's custom perpetual, with stats, liquidity, maker activity, and risk dashboards.
Prediction-market outcomes, questions, and resolutions across the full HIP-4 surface.
Integrating HIP-4 does not add another vendor. It unlocks complete Hyperliquid data access, from perp orderbooks to builder-deployed markets to prediction-market settlements, through one consistent surface.
Three standard tiers plus bespoke pricing for partners who need unlimited calls or custom Hyperliquid data. All tiers include full HIP-4 and Hyperliquid endpoint access and testnet APIs.
For recently launched apps
Best plan for scaling teams
For data-rich, large apps
Bespoke pricing for partners
Add-on features like extra market-data endpoints and allfills are available as separate purchases. See the full pricing page for details.
80+ teams on Hyperliquid already run on Hydromancer. Get an API key in minutes and start integrating Hyperliquid the same day.
HIP-4 is the Hyperliquid standard for registering prediction-market outcomes and questions natively on the L1. Outcomes are discrete yes/no or multi-sided markets; questions group outcomes with a fallback resolution path.
All five: outcomeMeta, registeredOutcomes, registeredOutcomesById, settledOutcomes, and settledOutcomesById, covering the full HIP-4 surface area.
HIP-3 lets builders deploy custom perpetual contracts on Hyperliquid. HIP-4 extends that to prediction-market outcomes and questions with discrete event contracts, on-chain settlement, and programmable oracles.
Yes. HIP-4 exposes binary outcomes, multi-outcome questions, and oracle-driven resolution on Hyperliquid's L1 with shared orderbook liquidity.
Yes. Hydromancer's HIP-4 endpoints share auth, request shape, and infrastructure with the core Hyperliquid DEX and HIP-3 stack.