Skip to main content

1. Generate an API key from your account

1

Log in

Log in at app.range.org. If you do not have an account, contact us to request access.
2

Open your API settings

Go to Settings > API (app.range.org/keys).
3

Generate your API key

Choose the API scopes you need, generate your key, and copy it.
Copy your API key when you generate it. Range shows it only once. You can revoke and rotate keys from your API settings.

API key scopes

For MCP, enable the Data API scope to connect. Enable all three scopes to use tools across all three APIs. Scopes do not grant write access.

Key types and workspace access

Keys generated at Settings > API are managed workspace keys. They carry no member or role and cannot call get_current_member or the four MCP mutating tools: add_accounts, create_counterparty, add_counterparty_addresses, and create_alert_rule. A workspace-user key is the credential used by a signed-in Range app session. The API keys page does not issue this type of key. Workspace-scoped tools cover accounts, balances, alerts, counterparties, transfer enrichment, and v2 screening; a legacy key cannot call them. See the Tools Reference for each tool’s requirements.

2. Authenticate

The documented authentication method for Data, Risk, Platform, and MCP requests is an API key in the Authorization header:
REST requests use the base URL https://api.range.org. The server also accepts X-API-KEY as a legacy header; use Bearer for new integrations and the examples in these docs.
Keep your API key server-side. Store it in an environment variable, never in client-side code or a public repository. Rotate it if it is exposed.
Set RANGE_API_KEY in your shell session, replacing YOUR_API_KEY with your key:

3. Make your first call

Choose a quickstart for a request and the response fields to check:

Data API

Look up a blockchain address.

Risk API

Screen an address for risk.

Platform API

List your workspace’s counterparties.

Range AI

Discover tools over MCP.
For failed requests, throttling, credit usage, and plan access, see Errors and rate limits.
Last modified on November 9, 2026