---
updatedAt: 2026-10-07T00:23:54.000Z
agentTools:
  projectIndex: https://readme.cipherowl.ai/llms.txt
---

# Introduction

What the CipherOwl SRR API (Screening, Risk & Reporting) does and where to start — build a client, run the investigation workflow, and find the reference. For developers and AI agents.

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](https://readme.cipherowl.ai/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](https://readme.cipherowl.ai/reference/build-a-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)](https://readme.cipherowl.ai/reference/sandbox-quickstart)** — run a full investigation end-to-end, for free, against curated sandbox addresses: screen → triage → evidence → report.
3. **[API Reference](https://readme.cipherowl.ai/reference)** — every endpoint, with request and response schemas.

Supporting pages: [Authentication](https://readme.cipherowl.ai/reference/authentication) · [Parameters](https://readme.cipherowl.ai/reference/parameters) · [Status Codes](https://readme.cipherowl.ai/reference/status-codes) · [Support](https://readme.cipherowl.ai/reference/support).

## Conventions

* **Base URL:** `https://svc.cipherowl.ai` for every endpoint. HTTPS is required for all requests.
* **Auth:** OAuth 2.0 client credentials → Bearer token. See [Build a CipherOwl Client](https://readme.cipherowl.ai/reference/build-a-client).
* **Format:** REST with JSON request and response bodies; mostly `GET`, plus `POST` / `PATCH` / `DELETE` where noted.
* **Chain or network:** every address-scoped URL names the blockchain at one of two levels, and the path tells you which.

  * `/chains/{chain}/…` takes a **chain** — a family of networks that share one address format, such as `evm`, `bitcoin` or `tron`. Risk is evaluated per chain, so Screening, Risk Reason, Report and Continuous Monitoring take a chain.
  * `/networks/{network}/…` takes a **network** — one specific blockchain, such as `ethereum_mainnet` or `bitcoin_mainnet`. Balances, transactions and recorded metadata live on a network, so the Onchain Service and Private Data APIs take a network.

  See [Parameters](https://readme.cipherowl.ai/reference/parameters) for the accepted values.