API profile

Range API

Range API is preserved in Discovery as a current public source profile for stablecoin, fiat, and onchain operations. Official docs describe account connections, address intelligence, blockchain transactions, balances, payments, risk and sanctions screening, alerting, and Range AI MCP tools. PubFi does not certify Range as a gateway route, credentialed supplier, x402 provider, or runtime integration

Indexed onlyProvider Profile

Decision guide

Use it when

Evaluating Range stablecoin, fiat, and onchain operations docs

Check first

Assuming PubFi gateway availability without adapter certification

PubFi status

Provider Profile

The page is an AI/Codex-processed public Provider Profile and does not claim PubFi integration, gateway access, x402 payment, or MCP tooling.

Key facts

Auth
Not listed
Pricing
Public commercial facts require product-specific review
Agent actionability
Not actionable
PubFi gateway
PubFi gateway not routeable yet
Last verified

Provider-sourced facts

Public docs evidence
Range official docs cover stablecoin and fiat operations, account connections, address intelligence, blockchain transactions, balances, payments, risk and sanctions screening, alerting, and MCP tools. Source
PubFi gateway status
Automation-built Provider Profile; PubFi gateway support is not certified.

Best fit and tradeoffs

Best for

  • Evaluating Range stablecoin, fiat, and onchain operations docs
  • Comparing address intelligence, risk, sanctions, and MCP source evidence
  • They want a public starting point for evaluating Range stablecoin, fiat, address intelligence, risk, sanctions, alerting, and MCP documentation.
  • They need to compare Range against onchain analytics, wallet-label, compliance, and agent-tooling sources before runtime integration work.
  • They want claim-safe evidence that separates Range public API and MCP docs from PubFi gateway or MCP runtime certification.

Watchouts

  • Assuming PubFi gateway availability without adapter certification
  • Treating Range MCP availability as PubFi MCP runtime support
  • The old Range risk reference URL now returns 404 to machine fetchers, so use the official docs index, Range AI docs, and endpoint-specific API docs for current evidence.
  • Public docs evidence does not prove credential availability, commercial approval, pricing, uptime, or PubFi gateway runtime support.
  • Teams should verify endpoint shape, authentication, quotas, MCP client requirements, and terms before treating Range as production-callable.

Why teams choose it

Range API is a current public source profile for stablecoin, fiat, onchain operations, address intelligence, sanctions, risk, alerting, and MCP evidence. Current official docs publish a machine-readable docs index plus Range AI MCP guidance for using an existing Range API key from MCP-compatible clients.

Discovery keeps this page claim-safe: inclusion means public Range evidence was processed into a Provider Profile, not that PubFi has certified gateway routing, credentials, x402 payment, PubFi MCP tooling, supplier procurement, or runtime support for Range.

What it can cover

Range API onchain risk and MCP evidence

Unproven
Category
On-chain state
Public status
Requested
Auth requirement
API key
Access review
Not Procurable
Coverage
Multichain
Output contracts
Onchain Risk Intelligence Profile

PubFi gateway

PubFi gateway not routeable yet

This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.

PubFi gateway call
Not published for this source
Direct gateway examples
Not available
Next step
Request integration or start supplier procurement review
  • Do not infer a PubFi gateway path from this Discovery page.
  • Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source production-callable.
  • Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
  • Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.

Implementation notes

Gotcha

High

Do not describe Range as a PubFi MCP route or certified gateway supplier; Range's own MCP endpoint is independent public provider evidence.

Docs

Medium

Use https://docs.range.org/llms.txt for the current machine-readable docs index and Range AI docs for MCP-specific evidence.

Coverage

Medium

Treat Range as source-selection evidence for stablecoin, fiat, address, transaction, risk, and sanctions workflows until PubFi runtime certification exists.

Use cases

  • Compare Range API evidence before runtime integration work
  • Assess whether Range address, transaction, risk, and sanctions endpoints fit an agent-readable source selection task

Comparison snapshot

Range API should be compared with onchain analytics, wallet-label, compliance, and AI-agent tooling providers. The current public evidence is strong enough for Discovery visibility and LLM export with source-profile wording, but not for certified PubFi gateway routing.

PubFi friction relief

Docs

Source friction
Range official docs expose a machine-readable index covering API reference, stablecoin and fiat operations, address intelligence, risk and sanctions, alerting, and Range AI MCP workflows.
PubFi relief
PubFi Discovery turns current public evidence into a claim-safe Provider Profile and separates Range's own MCP/API docs from PubFi gateway certification.

FAQ

Is Range API available through the PubFi gateway?

This Provider Profile is automation-built from public evidence and does not certify PubFi gateway availability.