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

# Pricing and Metering

> The per-request price, access tiers, service limits, and how Rangler meters your account.

## Pricing

Rangler API is billed per request: **₦1 per billable API request**.

A request is billable when it is made with a live key (`rgl_live_`) and returns:

| Response | Billed |
| - | - |
| `2xx` success | Yes |
| `4xx` client error, such as `404 Not Found` or `422 Unprocessable Entity` | Yes |
| `429 Too Many Requests` | No |
| `3xx` redirect | No |
| `5xx` server error | No |

Sandbox requests (`rgl_test_` keys) are never billed.

## Access tiers

| Tier | Access | Best for |
| - | - | - |
| Trial | Sandbox evaluation | Evaluating the API and testing your integration |
| Build | Live API access | First production workflow: fund pages, filing monitors, internal tools |
| Custom | Tailored access | Brokers, PFAs, banks, or any workflow that needs custom volume, routing, or SLA |

Tiers set your environments and service limits. They do not add charges on top of the per-request price. Production keys require live access.

## Service limits

Each tier has operational limits on the units below. They are service limits, not separate billing units.

| Unit | What it measures |
| - | - |
| Covered entities | Funds or issuers your organization actively tracks through subscriptions, routing, or workflow usage |
| Matched events | Events that match one of your active subscriptions or tracked entities |
| Deliveries | Webhook payloads sent to your configured endpoints |
| AI summaries | Optional generated summaries on top of event or fund updates |

If your usage approaches a service limit, you'll see it in the portal and we'll review the account with you. Rangler does not charge for workflow units when you go over a limit.

Connect is design-partner/custom during v1. We meter link sessions, active connections, refreshes, connected accounts, retained history, and webhook deliveries, but we do not publish a self-serve Connect package until provider access and support costs are proven.

## Request rate limits

Rangler enforces request rate limits separately from billing.

Every API response includes rate-limit headers:

```http theme={null}
X-RateLimit-Limit: 5000
X-RateLimit-Remaining: 4832
X-RateLimit-Reset: 1718323200
```

When you hit the request-rate limit, Rangler returns `429 Too Many Requests` with a `Retry-After` header. Rate-limited requests are not billed. See [Errors](/errors) for the response format.

| Tier | Daily request limit |
| - | - |
| Trial | 500 |
| Build | 5,000 |
| Custom | As agreed |

Rate limits apply at the organization level. All keys in your organization share the same daily budget.

## Checking your usage

The portal's API usage page shows your organization's requests by endpoint, request path, and API key, along with your billable live requests for the current month. Billing months run from midnight to midnight, West Africa Time (Africa/Lagos).

## Related pages

[Quickstart](/quickstart) covers your first request, [Authentication](/authentication) explains the API key model, [Environments](/environments) covers sandbox and live isolation, and [Errors](/errors) documents rate-limit headers and error responses.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.