Asynchronous freeze-risk intelligence API

The FreezeRadar Business API mirrors the same freeze-risk analysis used in the app. Every screening is asynchronous: a create call returns immediately with a job id, and the result becomes available once analysis finishes — via polling or a signed webhook event.

All endpoints below are relative to https://freezeradar.com/api/v1. The current version is v1; breaking changes will ship under a new version prefix rather than mutating this one.

Accepts the same address, chain, optional asset list, and optional scan mode as the FreezeRadar app. Returns immediately with an id and QUEUED status.

curl -X POST https://freezeradar.com/api/v1/address-screenings \
  -H "Authorization: Bearer fr_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "address": "0x…",
    "chain": "ethereum",
    "assets": ["USDT"],
    "scanMode": "STANDARD"
  }'

{
  "ok": true,
  "data": {
    "id": "scan_job_id",
    "status": "QUEUED",
    "resultUrl": "/api/v1/screenings/scan_job_id"
  }
}

Screens a specific on-chain transaction. Coverage is returned only where the underlying chain provider can prove a supported freezeable-asset transfer.

curl -X POST https://freezeradar.com/api/v1/transaction-screenings \
  -H "Authorization: Bearer fr_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "chain": "ethereum",
    "transactionHash": "0x…",
    "policyId": "cl…"
  }'

{
  "ok": true,
  "data": {
    "id": "screening_id",
    "status": "QUEUED",
    "resultUrl": "/api/v1/screenings/screening_id"
  }
}

A transaction that is valid but has no supported asset coverage, or cannot be assessed for that chain, returns 422 and releases its reserved quota.

Returns the latest job state for either screening type. Possible statuses are QUEUED, RUNNING, COMPLETED, and FAILED. Do not treat QUEUED or RUNNING as a final result.

curl https://freezeradar.com/api/v1/screenings/scan_job_id \
  -H "Authorization: Bearer fr_live_…"

{
  "ok": true,
  "data": {
    "id": "scan_job_id",
    "status": "COMPLETED",
    "resultUrl": "/scan/wallet_scan_id",
    "walletScanId": "wallet_scan_id",
    "errorMessage": null,
    "scan": {
      "id": "wallet_scan_id",
      "overallRisk": 62,
      "riskCategory": "MEDIUM",
      "confidenceScore": 0.81,
      "accessMode": "SUMMARY",
      "scanMode": "STANDARD",
      "analyzedAt": "2026-08-05T02:10:00.000Z"
    }
  }
}

{
  "ok": true,
  "data": {
    "id": "screening_id",
    "status": "COMPLETED",
    "verdict": "CLEAR",
    "riskCategory": "LOW",
    "overallRisk": 12,
    "chain": "ethereum",
    "transactionHash": "0x…",
    "resultUrl": "/api/v1/screenings/screening_id",
    "completedAt": "2026-08-05T02:10:00.000Z",
    "errorMessage": null,
    "result": { "findings": [], "transferCoverage": "…", "policyVersion": null }
  }
}

Transaction results include verdict (CLEAR / REVIEW / BLOCK), riskCategory, findings, transfer coverage, and the policy version when one was used. Responses never include raw evidence blobs.

Select events in the Business Developer Console. Payloads are JSON and include id, type, createdAt, and data.

Every delivery includes these headers. The signature is sha256= plus an HMAC-SHA256 of the timestamp, a dot, and the raw request body, using the webhook secret shown at creation.

import { createHmac, timingSafeEqual } from "node:crypto";

const signed = `${timestamp}.${rawBody}`;
const expected =
  "sha256=" +
  createHmac("sha256", webhookSecret).update(signed).digest("hex");

if (!timingSafeEqual(Buffer.from(signature), Buffer.from(expected))) {
  throw new Error("Invalid FreezeRadar signature");
}

Verify the signature against the raw body before parsing. Deduplicate on event id. Reject stale timestamps according to your replay window. Return any 2xx response to acknowledge delivery; non-2xx responses are retried with bounded backoff.

Usage is account-scoped. Keys remain hashed at rest but are rejected on use unless the account still has an active Business entitlement. A transaction screening that cannot start because it is invalid, unsupported, or provider-unavailable releases its reserved transaction quota. Bridge-trace and graph-explorer entitlements are plan flags for product gating; they are not exposed as separate public /api/v1 endpoints yet.