Introduction

CipherOwl exposes several APIs for blockchain compliance. This guide focuses on the SRR API — Screening, Risk & Reporting — which turns a blockchain address into a compliance decision: sanctions and risk screening, risk scoring, the evidence behind a verdict, and human-readable reports, across multiple chains.

📘

Other CipherOwl APIs

CipherOwl also offers the Onchain Service and Private Data API. They share the same authentication and are documented in the API Reference; this guide covers the SRR API.

This guide is written for both developers and AI agents. Each page is self-contained and states its contract explicitly, so an automated client can read a page and act on it without cross-referencing.

Start here

1. Build a CipherOwl Client — authenticate and create a client that caches its token, refreshes on 401, and backs off on 429. Copy-paste clients in Python, Go, TypeScript, and Java.
2. SRR Investigation Workflow (Sandbox) — run a full investigation end-to-end, for free, against curated sandbox addresses: screen → triage → evidence → report.
3. API Reference — every endpoint, with request and response schemas.

Supporting pages: Authentication · Parameters · Status Codes · Support.

Conventions

• Base URLs: https://svc.cipherowl.ai/api/. Each endpoint's reference page lists which base URL to use. HTTPS is required for all requests.
• Auth: OAuth 2.0 client credentials → Bearer token. See Build a CipherOwl Client.
• Format: REST with JSON request and response bodies; mostly GET, plus POST / PATCH / DELETE where noted.
• Chains: specify the blockchain with its chain key (for example evm or tron). See Parameters for the keys each endpoint accepts.