Range: treasury, risk, and compliance APIs for stablecoins — Solana included

Range: treasury, risk, and compliance for companies operating across stablecoins and fiat — one place to unify accounts, screen before money moves, and build on the same capabilities via API and MCP. Solana is a first-class network, not an afterthought.

Site: range.org. App: app.range.org. Docs: docs.range.org (llms.txt). API: api.range.org. X: @range_org. Status: status.range.org.

What it is

Range markets total financial control across stablecoins and fiat: connect wallets, custodians, exchanges, and bank accounts into one real-time ledger; run pre-execution controls; reconcile and classify transactions; manage counterparties with Travel Rule-style data; monitor portfolio and threat surface.

Public claims on the homepage/docs: $30B+ AUM protected, $20B+ payment volume screened per month, 10,000+ banks / custodians / wallets integrated. Named trust logos in docs include Solana Foundation, Circle, Stellar, Squads, Jupiter.

Product pillars finance teams see in the UI map cleanly to modules: Treasury, Reconciliation, Counterparties, Intelligence/reporting — plus Transaction Screening, Counterparty Risk, Threat/Fraud Prevention, Portfolio Risk.

Builder surface: four APIs

From Build on Range, availability depends on activated modules / plan:

Auth quickstart

1. Sign up at app.range.org.
2. Settings → API → generate key (app.range.org/keys) — shown once.
3. Send Authorization: Bearer <key> on every request.

# Data API — Solana address lookup
curl 'https://api.range.org/v1/address?address=CCTPiPYPc6AsJuwueEnWgSgucamXDZwBd53dQ11YiKX3&network=solana' \
  --header "Authorization: Bearer $RANGE_API_KEY"

# Risk API — classic address score on Solana
curl -G 'https://api.range.org/v1/risk/address' \
  --data-urlencode 'address=TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA' \
  --data-urlencode 'network=solana' \
  --header "Authorization: Bearer $RANGE_API_KEY"

# Platform — list counterparties
curl 'https://api.range.org/v2/counterparties' \
  --header "Authorization: Bearer $RANGE_API_KEY"

Full walkthrough: Quickstart.

Risk API — what Solana builders hit first

Risk API base URL https://api.range.org. High-signal endpoints:

• Address risk v2 — configurable severity, signals, evidence
• Address risk score v1 — classic 1–10 proximity score (Solana + EVM + Stellar + more)
• Payment risk assessment — end-to-end safety between two addresses (Solana, Stellar, Cosmos, …)
• Sanctions & blacklist — OFAC + issuer blacklists (ETH/Tron/Solana among others)
• Token risk assessment — multi-factor Solana token analysis (docs: 17 factors)
• Transaction simulator — simulate before broadcast (Solana, Osmosis, Neutron)
• Humanize transaction — plain-language explanation of a hash (Solana + Ethereum)

Pattern for product teams: screen destination + amount path in your backend before constructing the Solana transfer; optionally simulate; then sign.

Protect / alerting — Squads-native ops

Range Protect is a catalogue of alert rules you point at accounts and route to Slack, Discord, webhooks, email, PagerDuty, Telegram, etc. Categories include treasury/asset monitoring, sanctions, stablecoins, program security, and multisig governance — Squads, Safe, Realms lifecycle (proposals, approvals, member/threshold changes, timelocks, vault flows).

Platform API can create/list rules and channels; account connections support squads / safe / realms multisig types. Squads CEO quote on the marketing site frames Range as OpenSec infrastructure integrated into Solana products — treat that as product positioning, verify integration depth against current API docs for your vault program id.

MCP for agents

Same API key → Range AI MCP server:

MCP endpoint (Streamable HTTP)
https://api.range.org/ai/mcp

Auth: Authorization: Bearer <key>
      (or x-api-key: <key>)

~85 tools — workspace data, risk/sanctions, investigations
Mostly read-only; a few mutating tools need EDITOR+ workspace key

Docs recommend enabling Risk + Data + Platform scopes on the key for full MCP visibility. Quickstart covers Claude / Cursor wiring: AI Quickstart. Investigation playbook exists for wallet-to-report workflows.

This sits in the same agent-infra lane as PayBox (spend), Avici (read-only neobank), Bitbond MCP (issuance) — Range is risk + treasury intelligence.

Mental model

Banks / Plaid / Wise
Exchanges / Fireblocks / Cubist
On-chain wallets + Squads / Safe
        \
         → Range workspace ledger
              ├── UI: treasury, recon, counterparties
              ├── Protect alerts → Slack/PagerDuty/...
              ├── Risk screen before send
              ├── Faraday: compliant cross-chain stables
              └── API + MCP for your apps/agents

When to use Range vs DIY

• Use Range — need sanctions/risk as a service, multi-rail treasury visibility, Squads/Safe alerting, or agent MCP without standing up your own graph DB + OFAC pipeline.
• DIY / chain-native — pure protocol research with public RPCs, or you already run Chainalysis/TRM-class stack and only need Solana indexers.
• Compose — Range Risk in your payment API; Streamflow / Bitbond for distribution/issuance; Clerk for app users.

Practical start for a Solana product

1. Create workspace + API key with Risk (and Data if you want graphs).
2. Wire GET /v1/risk/address?network=solana (or v2) on withdraw/deposit counterparties.
3. Optional: Solana tx simulator before broadcast for high-value paths.
4. Connect Squads vaults → enable multisig alert catalogue → Slack.
5. Point coding agents at https://api.range.org/ai/mcp for investigation assist.

Resources

• range.org · Docs
• API Quickstart · Risk API
• MCP / AI Quickstart · MCP tools reference
• Alerting / Protect · Multisig monitoring guidelines
• Sybil / identity options · PayBox MCP
• Range on DevRels

Bottom line

Range is the compliance-and-treasury layer many Solana fintechs eventually rebuild poorly: unified balances across rails, risk scores before send, Squads-aware ops alerts, and an API/MCP surface that drops into product backends and agent workflows. Start with a Risk API screen on Solana counterparties; grow into Platform connections and Protect once treasury ops hurt.