Raw Hyperliquid data won't ship your app. mute will.
On-chain, your markets are hex codes buried in AMM noise — no names, no scores, no push. mute hands your app what users actually see: the market by name, the live score inside the feed, and a lock-screen push the second a bet fills. One key, live today.
Try the live feed — no key needed
Building a consumer app? Enterprise starts here →
Your users can see the goal on TV. Can your app?
A World Cup knockout goal moves the market 40 cents in under a minute. If your feed is a cached dump or the public info endpoint, your users watch the odds jump on Twitter before your app repaints. They screenshot it. They churn. Every stale second is builder revenue walking out the door.
A trade fills. Your app already has it.
Every fill, read at the source the instant its block lands — not the hours-old dumps resellers hand you. Your app is never the last to know.
Complete — and you can prove it.
Every trade since these markets opened, with no silent holes to build on. Pull the archive and audit any fill against the chain, block by block.
“Mexico vs England,” not “#7380.”
A coin id means nothing to your users. Markets arrive with the real name, teams, and settlement — screens that read like a product, not a database dump.
Analytics for your users. Revenue answers for you.
Per-user volume, P&L and win rate, ready to render in-app. And every fill carries the app that sent it — you see exactly what your front-end drives and what it earns you.
The head start no one else can sell you.
Everything below this line exists nowhere else — not on-chain, not in a raw dump, not from a reseller: the result at the whistle, the settlement vote as it's cast, the block as it's produced, and a filtered push of every trade that matters. It isn't node output — it's the pipeline on top. That's the part you can't stand up.
Enterprise planWhistle. Your user's bet just won.
On-chain settlement will confirm it in hours — sometimes half a day.
With mute, your app pays out the celebration now. Without it, your winning user stares at “pending” — and opens your competitor.
Your market feed, with the match built in.
The sports markets on Hyperliquid, joined to the live game. One call gives your screen the score, the minute, and every price — and your server hears the goal the moment it's scored.
- Live score and match minute, right inside your own market cards.is_live · match_minute · live fixture join
- Goals, cards and VAR pushed to your server the second they happen — signed, and retried until they land.match.goal · match.card · match.var webhooks
- News headlines and video highlights for every fixture, ready to drop in./v1/sports/fixtures/:id/news · /highlights
{"coin":"#7380","px":"0.73","sz":"18240","dir":"Buy"}
{"coin":"#7380","px":"1.0","dir":"Negate Outcome"} ← not a bet
{"coin":"#7381","px":"0.27","dir":"Split Outcome"} ← AMM noise
no name · no match · no score · no result
Watch the result get decided, vote by vote.
The instant validators start voting to settle a market, you see it — who's voting, how much they've staked, and the plain-English reason: “FIFA officially declared Mexico the winner.” All while the coins are still trading.
Block-speed data, for when milliseconds pay.
New blocks streamed the instant they reach our node — one hot connection, straight from the machine that sees them first. Built for trading systems and indexers that can't wait on a refresh.
Any bet over $10k, on any market — pushed to you.
Describe the trades you care about in plain terms — size, side, market, or any mix — and we push only those, across the entire network. Order events, not just fills. Every delivery is logged, with one-click replay if your server was down.
Pay for liquidity. We keep the score.
Run a rewards program on your own builder code — the growth playbook that bootstraps every serious market. You fund the pool and pick the markets; we score every fill from the chain, throw out wash trading and self-matches, serve the live leaderboard your app renders, and hand you the exact payout file each cycle. Deeper books bring takers, and taker exits through your front-end are what pay your builder fee.
Custom pricing — typically less than your build-it-yourself sports license alone.
A founder replies within one business day. You talk to the people who run the node — there is no sales team.
Where the line is.
Same key and full archive on every plan. Everything your users can feel — the match, the result, the push — is above the line.
| Capability | Free | Growth | Scale | Enterprise |
|---|---|---|---|---|
| Named markets, full archive | ||||
| Requests / minute | 10 | 1,000 | 3,000 | 50,000 |
| Monthly tokens | 1,000 | 1M≈ ~300 DAU | 3M≈ ~1,000 DAU | Uncappedno token math |
| Alert feeds — lock-screen push | — | — | 10 feeds~1,000 users total | Unlimited+ filters · firehose · replay |
| Live sports — score, minute, events | — | — | — | |
| Result at the whistle (is_concluded) | — | — | — | |
| L1 settlement votes, live | — | — | — | |
| gRPC block stream | — | — | — | |
| Liquidity rewards engine (your builder code) | — | — | — | early access |
| Macro & crypto market context | — | — | — | |
| Founders group · bespoke endpoints · Net-30 | — | — | — |
Sure, build it yourself — it's only $15k/mo and six months. Here's the receipt.
This is the bill for standing up what one mute key hands you on day one.
Build it
- Hyperliquid mainnet node — co-located Tokyo bare metal, bandwidth, snapshots, a pager that goes off at 4am$1.5–2.5k/mo
- AWS data stack — ingest, columnar store, streaming, backups, monitoring. Grows with every block, forever$2–4k/mo
- Live sports data license — fixtures, scores, match events. Real-time tiers are priced for sportsbooks$1.5–5k/mo
- Macro & crypto market data APIs — prices, oracle context, protocol series$0.5–2k/mo
- News & video highlights feeds — licensed, per-fixture, rate-limited$0.5–1.5k/mo
- Then the hard part: parse every block, reverse-engineer the coin↔market mapping, strip the AMM noise from real trades, match fixtures to markets by hand, build signed delivery with retries — and keep ALL of it alive through every network upgrade2+ engineers
$6,000–15,000/mo in vendors before a single salary — and 4–6 months of engineering before your first feature ships.
One API key
- The node, the data stack, the 4am pager — already ours.
- Sports, macro and news licenses — already carried, by us. Enterprise
- The coin↔market decoder ring — already built, kept current through every upgrade.
- The AMM noise stripped, fixtures matched to markets — already done, daily.
- Signed delivery with retries — already landing on servers like yours. Scale+
- 99.9% uptime SLA — someone else's 4am, contractually.
You ship your app. Not a pipeline.
api.mute.sh · grpc.mute.sh · webhooks
Week one, in practice
- DAY 1 key → live named markets
- DAY 2 scoreboard in-app
- DAY 3 fill-push on lock screens
That's the outcome.xyz timeline.
Every serious app ends up on Enterprise. Start where you are.
Free is for evaluating. Growth is for dashboards. Scale is for a closed beta. Enterprise is for an app with real users. Get a key in minutes — no waitlist, nothing to pay up front. Paid plans settle in crypto.
Free
For evaluating. Nothing to pay.
- 10 requests / min
- 1,000 tokens / mo
stops at the cap · resets monthly - Every core endpoint, full archive
Growth
For dashboards & research — not apps.
- 1,000 requests / min
- 1M tokens / mo
supports ~300 DAU · fine for a dashboard - Builder & group analytics
- Full history archive
- Overage $22 / 100k — never cut off
Not included
- No push. Your app can't notify anyone — alerts start on Scale
- No enriched data. No sports, no live scores, no votes, no context
Scale
For a closed beta — 1,000 users, by design.
- 3,000 requests / min
- 3M tokens / mo
~1,000 DAU · a closed beta, by design - 10 alert feeds · 100 users each
lock-screen push · ~1,000 users total - Everything in Growth
- Bulk backfill · on-call paging
- Overage $9 / 100k — never cut off
Not included
- Still no enriched data. Names, yes — but no match, no score, no result-at-the-whistle
- 1,000-user hard ceiling. A consumer app passes that fast — that's Enterprise
Enterprise
For an app with real users.
- Unlimited. No token math. No DAU ceiling.
fair use · 50,000 req/min - Live sports — score, minute, goals, cards, VAR
/v1/sports/* - Result at the whistle
is_concluded — hours before on-chain settlement - L1 settlement votes, live
/v1/l1-votes/* - gRPC block stream
grpc.mute.sh - Macro & crypto context — oracle prices, DefiLlama-derived series
- Unlimited alert feeds + filters, firehose, order events, replay
- Private founders group · bespoke endpoints · Net-30
Every paid tier includes the full history archive since 2026-05-02 · 99.9% uptime SLA. The private founders group is Enterprise-only. Full plan details in the docs ↗
100+ endpoints. One key.
Live in your app this afternoon. Everything you'd otherwise stitch together from five vendors — markets, people, sports, context, delivery — behind one X-API-Key. Ask for it over REST, watch it over SSE, or have it pushed.
base https://api.mute.sh · full API reference ↗
# one enriched market, prices per side curl -s https://api.mute.sh/v1/outcomes/451 \ -H 'X-API-Key: mute_live_•••'
{
"id": "451",
"class": "sports",
"question": "Will ARG win the final?",
"sides": [
{ "side": "A", "label": "Yes", "px": 0.62 },
{ "side": "B", "label": "No", "px": 0.38 }
],
"volume": 675114,
"traders": 1394,
"settlement": null,
"recent_trades": [
{ "side": "A", "px": 0.62, "notional": 4120 }
]
}
# which apps drive the volume — and what it earns them curl -s https://api.mute.sh/v1/analytics/leaderboard/builders \ -H 'X-API-Key: mute_live_•••'
{
"builders": [
{ "builder": "outcome.xyz",
"volume_7d": 4812932,
"users": 2210,
"fills": 88412 },
{ "builder": "…" }
]
}
# sportsbook-ready cards: score, minute, result curl -s https://api.mute.sh/v1/sports/match-markets \ -H 'X-API-Key: mute_live_•••'
{
"fixture": "Mexico vs England",
"competition": "World Cup · R16",
"score": [2, 1],
"match_minute": 74,
"is_live": true,
"is_concluded": false,
"markets": [
{ "name": "Mexico to win", "px": 0.73 },
{ "name": "England to win", "px": 0.28 }
]
}
# crypto price markets, joined to the oracle curl -s https://api.mute.sh/v1/crypto/price-markets \ -H 'X-API-Key: mute_live_•••'
{
"underlying": "BTC",
"mark_px": 118432.5,
"markets": [
{ "name": "BTC ≥ $120k by Friday",
"px": 0.41,
"distance_to_target": "-1.3%" }
]
}
# a bet fills → your server knows, signed curl -X POST https://api.mute.sh/v1/webhooks/subscriptions \ -H 'X-API-Key: mute_live_•••' \ -d '{"url":"https://your-server/hooks", "events":["fill","settlement"], "wallets":["0xab12…"]}'
# POST your-server/hooks · X-HL-Signature: sha256=… { "event": "fill", "market": "France to win", "px": 0.28, "notional": 12000, "wallet": "0xab12…" }
Why alert feeds matter when your app lives on a phone: a mobile app can't hold a connection open in the background — the OS kills it. So we POST the signed event to your server, your server fires the push, and your user sees “Your bet just filled” on their lock screen while the market is still moving. Alert feeds come with Scale; filters, order events, delivery history & replay come with Enterprise.
The questions buyers actually ask.
What happens if your node goes down?
The pipeline is monitored around the clock and pages the people who built it — directly, not through a ticket queue. Because everything is reconciled against the chain block by block, an interruption can delay data but can't silently lose it: when we're behind, we catch up and your archive stays complete. Paid plans carry a 99.9% uptime SLA; Enterprise adds direct on-call paging.
Where does the sports data come from — is it licensed?
Licensed real-time sports feeds — the tier priced for sportsbooks — joined to on-chain markets by our pipeline. We carry the licensing cost inside Enterprise; you don't sign a sports-data contract, we do. That single license is typically more than an Enterprise plan on its own.
Can we try Enterprise before committing?
Yes. Start on Free today to evaluate the core API — no payment, full archive. For the Enterprise feeds (sports, votes, gRPC), email admin@mute.sh and a founder will scope a trial against your real use case — usually within one business day.
What does the 99.9% SLA actually get me?
A commitment in the agreement, not a slogan on a page. Every paid plan carries the SLA; Enterprise agreements spell out the remedy — and Enterprise customers page the on-call founder directly when anything looks wrong. There is no sales team and no support tier between you and the people running the node.
How is this different from the public Hyperliquid endpoints?
The public info endpoint hands you raw coins: hex ids, AMM noise mixed into the trades, limited history, weight-based rate limits — and nothing about the real world. mute records the chain at the source, reconciles it, strips the noise, attaches the layer your users actually see (names, matches, scores, votes, context), and delivers it your way: REST · SSE · webhooks · gRPC.
What happens when I hit my token cap?
Paid plans never cut you off — past your allowance you pay the published overage ($22 per extra 100k on Growth, $9 on Scale), and every response carries X-Quota-Remaining so you're never surprised. Free hard-stops until the month resets. If you're doing overage math more than once, you're an Enterprise app — that's what uncapped is for.
Wire your app to the real tape.
The tape below is live money moving through the pipe right now. Two doors in: self-serve in minutes, or a founder within one business day.