# GET /v1/pro/*

Pro mirror of the data routes with its own rate tier; the page states whether calls are currently paid.

## Purpose

Every data route is mirrored under `/v1/pro` with the same parameters and response bodies, counted in its own `pro` rate tier. The paid MCP endpoint `/mcp/pro` offers the same tools as `/mcp`. Paid access is announced but not active: pro routes currently serve free data, identical to the free routes, and no payment is required.

## Paid access

Pro routes currently serve free data: no payment is required and none is charged, and `https://api.criptonlabs.com/mcp/pro` behaves the same. Paid access via x402 is announced but not active; the [payments guide](https://api.criptonlabs.com/docs/guides/payments.md) explains how paying will work and this page lists the prices once it is activated. `GET https://api.criptonlabs.com/v1/pro/requirements?resource=<path>` is free and returns the current `accepts` (`resource` may also be `mcp://criptonlabs/pro/<tool>`). Without `resource` it returns the price index: every paid route and tool with its price and links. It is counted in the `cheap` rate tier and is never charged.

## When to use

When you were told to use the pro namespace or need its own rate limit; the free routes carry the same data.

## When not to use

Do not rely on it for anything the free routes do not offer; there are no extra fields.

## Parameters

This endpoint takes no parameters.

## Request example

```sh
curl -s "https://api.criptonlabs.com/v1/pro/xrpl/fee"
```

This request needs no payment and returns the same data as the free route.

## Response example (200)

```json
{
  "fee": {
    "economy": "10",
    "standard": "10",
    "priority": "11"
  },
  "congestion": {
    "score": 4,
    "band": "low",
    "load_factor_assumed": false
  },
  "base_fee": "10",
  "median_fee": "5000",
  "minimum_fee": "10",
  "open_ledger_fee": "10",
  "current_queue_size": "0",
  "max_queue_size": "2000",
  "meta": {
    "ledger_index": 100234567,
    "as_of": "2026-10-06T12:00:03.000Z",
    "age_seconds": 1,
    "cache": "hit",
    "stale": false
  }
}
```

## Errors

- 400 [invalid-parameters](https://api.criptonlabs.com/errors/invalid-parameters.md)
- 400 [bad-request](https://api.criptonlabs.com/errors/bad-request.md)
- 404 [not-found](https://api.criptonlabs.com/errors/not-found.md)
- 429 [rate-limited](https://api.criptonlabs.com/errors/rate-limited.md)
- 503 [upstream-unavailable](https://api.criptonlabs.com/errors/upstream-unavailable.md)

## Caching

Same as the corresponding free route: fee, ledger and health 4 s fresh, 60 s max-stale; order book and slippage 4 s fresh, 30 s max-stale; AMM 8 s fresh, 60 s max-stale; account summary 10 s fresh, 120 s max-stale. See the [freshness guide](https://api.criptonlabs.com/docs/guides/freshness.md). Paid answers (a 200 that carried a settled payment, and every 402 challenge) carry `Cache-Control: no-store`.

## Rate limit

Tier `pro`. See the [rate-limits guide](https://api.criptonlabs.com/docs/guides/rate-limits.md).

## MCP tool

There is no MCP tool for this endpoint pattern; the paid MCP endpoint `/mcp/pro` exposes the same tools as `/mcp`. See the [MCP quickstart](https://api.criptonlabs.com/docs/guides/mcp-quickstart.md).