Real-time risk verdict for any on-chain address. <500ms.
Pre-transaction safety check for wallets, dApps, and DEX aggregators. Sanctions, scam, phishing, contract risk — answered in a single API call.
One call, one verdict, your decision.
Oracle returns a verdict shape designed for action, not exploration.
GET /v1/oracle/address/{chain}/{address}. Bearer API key. Works from server, edge, or browser.
safe | warning | danger | unknown — plus a 0-100 score, confidence tier, and human-readable reasons.
Block, warn, or allow. The verdict is your signal; the policy is yours. Confidence tiering keeps it auditable.
From request to decision in five lines.
REST API. Sample uses fetch — official TS SDK on the way.
// curl
curl -H "Authorization: Bearer ba_live_..." \
https://blockchainanalysis.io/api/v1/oracle/address/eth/0xabc...
// TypeScript (drop-in)
const res = await fetch(
`https://blockchainanalysis.io/api/v1/oracle/address/${chain}/${address}`,
{ headers: { Authorization: `Bearer ${ORACLE_KEY}` } }
);
const verdict = await res.json();
// { verdict: 'danger' | 'warning' | 'safe' | 'unknown',
// score: 0-100, confidence: 'high' | ..., reasons: [...],
// categories: [...], evidence: {...}, meta: {...} }
if (verdict.verdict === 'danger') blockTransaction(verdict.reasons);Full schema, examples, and error responses in the OpenAPI spec. Open the spec →
Built for compliance-grade integrations.
Differentiated by methodology depth, not heuristic count.
OFAC, EU FSF, UN SC, UK HMT, Swiss SECO. Direct match or fuzzy, with source attribution. Most providers cover only OFAC.
Every danger verdict is backed by a high-confidence labeled source. Inferred labels (clustering, 2-hop) are capped at warning. Auditable end-to-end.
Multi-chain entity coverage: exchanges, mixers, sanctioned, scam, phishing, ransomware — sourced and date-stamped.
Hot-path Redis cache, in-memory bloom for sanctions, deterministic verdict logic. No LLM in the request path.
Verdict shape is immutable in v1. Additive changes only. Customer integrations don't break under us.
Operating entity in EU/UK. Relevant if you're a MiCA-licensed CASP or a compliance-conscious wallet provider.
Integrations that need a verdict, not a report.
Oracle is API-first. UI products live elsewhere in the suite.
Pre-sign safety check. Warn or block before the user signs a transaction to a flagged address.
Verify counterparties at interaction time. Catch sanctioned addresses or scam contracts before settlement.
Route safety check. Avoid routing through risky pools or compromised wallets.
Onboarding-time and transaction-time safety, delivered as shared infrastructure your apps already trust.
Pay for what you use.
Free tier for evaluation. Indicative pricing — full table on the pricing page.
When to use Oracle, when to use KYT.
Oracle answers "is this safe NOW?" for consumer protection — wallets, dApps, DEX aggregators. KYT answers "can I process this transaction, and can I prove it in an audit?" for regulated VASPs, CASPs, and OTC desks. Oracle is fast and decision-shaped; KYT is compliance-grade with audit trail and FIU-ready reports. Same data backbone, different surfaces.
Common questions
Ready to integrate?
Request Access for early integration or to be notified at GA.
Request Access