> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meridiandata.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Pricing and request limits

> Understand Meridian's pay-per-call pricing, spend controls, and bounded Execute contract.

Meridian is sold through Context Protocol without a Meridian subscription. Context discovery and the execution response are authoritative for the current price.

## Current launch pricing

| Mode           |    Current price | Billing unit                |
| -------------- | ---------------: | --------------------------- |
| Direct Execute |         `$0.001` | Each successful method call |
| Managed Query  | Shown by Context | Each Context response turn  |

Direct Execute is intended for applications that already know the method and arguments. Query mode includes Context's method selection, evidence verification, and answer assembly, so its response price is configured independently from the Execute method price.

Context Protocol states that contributors receive 90% of eligible usage fees. At the current Execute price, Meridian's gross contributor revenue is therefore approximately `$0.0009` per successful call before infrastructure, tax, and operating costs.

## Buyer cost examples

| Successful Execute calls per month | Buyer spend | Approximate Meridian revenue |
| ---------------------------------: | ----------: | ---------------------------: |
|                              1,000 |     `$1.00` |                      `$0.90` |
|                             10,000 |    `$10.00` |                      `$9.00` |
|                             39,800 |    `$39.80` |                     `$35.82` |
|                            100,000 |   `$100.00` |                     `$90.00` |
|                          1,000,000 | `$1,000.00` |                    `$900.00` |

Velo documents its API subscription at `$199` per month. One fifth of that subscription is `$39.80`, equal to 39,800 Meridian Execute calls at the launch price. This comparison is usage-dependent: Meridian is not claiming unlimited access for one fifth of a subscription price.

## Profitability formula

Use this formula for planning:

```text theme={null}
break_even_calls = monthly_incremental_cost / 0.0009
```

Examples:

| Monthly incremental Meridian cost | Calls required to recover it |
| --------------------------------: | ---------------------------: |
|                             `$50` |                       55,556 |
|                            `$100` |                      111,112 |
|                            `$200` |                      222,223 |
|                            `$300` |                      333,334 |

These are planning examples, not revenue promises. Measure database CPU, response bytes, support time, storage growth, and Context settlement before changing the launch price.

## Request boundary

A single `futures` or `spot` Execute call is limited to 22,500 estimated metric values:

```text theme={null}
estimated values = time buckets x requested products x exchanges x metric columns
```

An over-limit request returns zero rows and a structured warning explaining how to narrow it. The boundary keeps latency and infrastructure cost predictable while still allowing the complete 51-product M2 universe to be audited in a bounded one-hour request.

## Spend controls

* Set `maxSpendUsd` or `max_spend_usd` on every application session.
* Use a unique idempotency key when retrying a call.
* Respect the method's discovered rate and concurrency hints.
* Close one-shot sessions after settlement.
* Read the charged amount from the execution result rather than hard-coding billing assumptions.

<Note>
  See the [Context contributor documentation](https://docs.ctxprotocol.com/guides/build-tools) for settlement rules and the [Velo API documentation](https://docs.velo.xyz/api) for its current subscription terms.
</Note>