> For the complete documentation index, see [llms.txt](https://mute-sh.gitbook.io/mute.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mute-sh.gitbook.io/mute.sh/api/getting-started/pricing.md).

# Pricing & Tiers

One **token = one API request**. Every plan meters two things: a **per-minute rate limit** and a **monthly token quota**. The live plan matrix is always available (no key needed) at [`GET /v1/pricing`](https://api.mute.sh/v1/pricing) — what follows is that data, explained.

## Plans

|                        | **Free**       | **Growth**           | **Scale**                          | **Enterprise**             |
| ---------------------- | -------------- | -------------------- | ---------------------------------- | -------------------------- |
| Price / month          | $0             | $1,100               | $2,300                             | custom                     |
| Requests / min         | 10             | 1,000                | 3,000                              | 50,000                     |
| Tokens / month         | 1,000          | 1M                   | 3M                                 | unlimited (fair use)       |
| Overage per extra 100k | — (hard-stops) | $22                  | $9                                 | —                          |
| History depth          | full           | full                 | full                               | full                       |
| Webhooks               | —              | —                    | 10 feeds × 100 users each          | unlimited + power features |
| Best for               | evaluation     | read-side dashboards | small apps (≤1,000 notified users) | consumer apps at scale     |

All paid tiers include the **full archive** — every endpoint over all HIP-4 history since launch (2026-05-02). There is no shortened history window on cheaper plans. Every paid plan comes with a **99.9% uptime SLA**. Direct founder access — a private shared group with the founders who run the node — is an **Enterprise** benefit. Get a key and manage billing at [app.mute.sh](https://app.mute.sh); for Enterprise, contact the team.

## What each step up buys you

* **Free → Growth**: 1,000 req/min (up from 10) and 1M tokens/month (up from 1,000). The free tier hard-stops at its quota; Growth flows into metered overage instead ($22 per extra 100k), so a traffic spike degrades your bill, not your app. Growth also unlocks **builder & group analytics** — `/v1/analytics/leaderboard/builders` and the `/v1/groups/*` P\&L and volume rollups. Growth is a **read-side plan** — dashboards, analytics, research. It has no push layer, so it can't drive notifications in a consumer app.
* **Growth → Scale**: 3× the tokens (3M), 3,000 req/min, and cheaper overage ($9 per 100k). Scale adds **bulk backfill** (historical delivery as S3/Parquet on request), the ability to **page the team** directly for critical incidents, and the headline: **webhooks**. Prediction-market apps are mobile apps, and a phone can't hold a stream open — the OS kills background connections in seconds. Webhooks are how your app stays alive: mute POSTs the signed event to your server the instant a watched bet fills or a market settles, your server fires the push, and your user sees *"Your bet just filled ✅"* on the lock screen. Scale includes **10 alert feeds watching up to 100 users each** (at most \~1,000 notified users), over HTTP or Telegram. That fits a closed beta or a small app; a consumer app with a real user base outgrows it — that's what Enterprise is for.
* **Scale → Enterprise**: fair-use unlimited tokens with custom rate limits, plus the full Enterprise surface:
  * **gRPC block streaming** (`grpc.mute.sh`) — sub-second HyperEVM block headers + HyperCore block markers
  * **Enriched sports feeds** — `/v1/sports/*`: HIP-4 sports markets joined to live fixtures (scores, kickoff status, match events, news, highlights)
  * **Live L1 settlement votes** — `/v1/l1-votes/*`: the validator votes that settle markets, seen while the coins are still trading
  * **Webhook power features** — order-status events, delivery history, replay, automatic retries, predicate filters (px/size/USD comparisons with AND/OR groups), and the whole-market firehose; **unlimited feeds and unlimited users watched**
  * **Macro & market-context enrichment** — DefiLlama-derived protocol series (`/v1/defillama/*`) and crypto price/oracle context (`/v1/markpx/*`, `/v1/crypto/price-markets`) are available across tiers, but Enterprise gets the richest, bespoke shaping of them — custom aggregations, oracle context, and delivery tuned to your integration
  * **Bespoke endpoints**, bulk S3/Parquet delivery, and invoice (net-30) billing

## Overage

Paid plans **never hard-stop** at the monthly quota — additional usage is billed at the published per-100k rate ($22 Growth, $9 Scale). Only the **free tier hard-stops** with `429` until the month rolls over. Enterprise runs on fair-use soft limits. Watch `X-Quota-Remaining` on every response to pace batch jobs — see [Rate limits & quotas](/mute.sh/api/getting-started/rate-limits.md).

## Webhook allowances

Webhooks are a **Scale and Enterprise** capability — the push layer that lets a mobile app deliver *"your bet just filled"* / *"the market settled"* the moment it happens, without polling a phone flat. Free and Growth keys authenticate fine but get a `403` naming the Scale requirement when they try to create one (see [Webhooks](/mute.sh/api/api-reference/webhooks-telegram-and-account.md)).

| Tier       | Webhooks | Alert feeds | Users watched per feed | Power features (order events · delivery history · replay · retries · predicates · firehose) |
| ---------- | -------- | ----------- | ---------------------- | ------------------------------------------------------------------------------------------- |
| Free       | —        | —           | —                      | —                                                                                           |
| Growth     | —        | —           | —                      | —                                                                                           |
| Scale      | ✓        | 10          | 100                    | —                                                                                           |
| Enterprise | ✓        | unlimited   | unlimited              | ✓ all                                                                                       |

An **alert feed** is one webhook subscription; **users watched** are the wallet/builder addresses it fires on. Enterprise removes both caps and adds the power features — signed order-status events, a failed-delivery log with replay, automatic retries, server-side predicate filters, and the network-wide firehose.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mute-sh.gitbook.io/mute.sh/api/getting-started/pricing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.