# CipherOwl - Developers Documentation Documentation > Documentation for CipherOwl - Developers Documentation ## API Reference - [Introduction](https://readme.cipherowl.ai/reference/introduction.md): 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. - [Authentication](https://readme.cipherowl.ai/reference/authentication.md): Obtain an OAuth 2.0 client-credentials access token for the CipherOwl API and use it as a Bearer token. For full client code in Python, Go, TypeScript, and Java, see Build a CipherOwl Client. - [Build a CipherOwl Client](https://readme.cipherowl.ai/reference/build-a-client.md): How to build a correct CipherOwl API client — OAuth2 client-credentials token flow, token caching and refresh-on-401, rate-limit backoff, required headers, and base URLs — with copy-paste clients in Python, Go, TypeScript, and Java. - [SRR Investigation Workflow (Sandbox)](https://readme.cipherowl.ai/reference/sandbox-quickstart.md): Run a full crypto-compliance investigation end-to-end for free — authenticate, screen an address, triage it with risk score and breakdown, pull the evidence with risk detail, and generate a report — using the co-sandbox config against curated EVM and Tron addresses. - [Parameters](https://readme.cipherowl.ai/reference/parameters.md): Common CipherOwl API request parameters — the chain key, address, config, hops, and namespace — and their accepted values. - [Status Codes](https://readme.cipherowl.ai/reference/status-codes.md): HTTP status codes returned by the CipherOwl API and what each means for your client — 200 success, 400 fix the request, 401 re-authenticate, 403 forbidden, 429 back off, 5xx retry. - [Support](https://readme.cipherowl.ai/reference/support.md): How to get help with the CipherOwl API — support contact and feedback form. - [Release Notes](https://readme.cipherowl.ai/reference/release-notes.md): Release notes for the CipherOwl public API — new endpoints, changes, and fixes by version. - [List overrides](https://readme.cipherowl.ai/reference/privatedataservice_listentriesforchain.md) - [Upsert override](https://readme.cipherowl.ai/reference/privatedataservice_upsertentry.md) - [Get override](https://readme.cipherowl.ai/reference/privatedataservice_getentry.md) - [Delete override](https://readme.cipherowl.ai/reference/privatedataservice_deleteentry.md) - [Screen address](https://readme.cipherowl.ai/reference/screenservice_screenaddress.md): Screens a single blockchain address against a risk configuration and returns a fast yes/no risk verdict (`found_risk`). This is the lowest-latency SRR endpoint, intended for real-time compliance checks such as gating a deposit, withdrawal, or counterparty before a transaction is allowed. - [Batch screen](https://readme.cipherowl.ai/reference/screenservice_batchscreenaddresses.md): Screens many addresses in a single request against one risk configuration, returning an independent risk verdict for each address. Use it for bulk or periodic re-screening of large address lists (for example, a customer wallet base or a watchlist) where per-address round trips would be too slow. - [Get risk detail](https://readme.cipherowl.ai/reference/riskreasonservice_getaddressriskreasondetail.md): Returns the most detailed risk explanation for an address. For each matched risk category and transaction direction it includes the number of hops to the risky entity, total USD and percentage exposure, first/last exposure timestamps, and the actual transaction paths (including cross-chain paths) connecting the address to risky entities. Use it when you need the full evidence behind a risky verdict — for investigations, case files, or audit trails. - [Get risk breakdown](https://readme.cipherowl.ai/reference/riskreasonservice_getaddressriskbreakdown2.md): Returns a categorized summary of an address's risk exposures — the set of matched risk categories and whether each exposure is direct or indirect — without the full per-path evidence. It is a lighter-weight view than the detail endpoint, intended for rendering an at-a-glance risk profile or dashboard for an address. - [Get risk score](https://readme.cipherowl.ai/reference/riskreasonservice_getaddressriskscore.md): Computes a deterministic 0–100 risk score for an address from its exposure profile. Use it for risk tiering, threshold-based alerting, and automated decisioning where a single comparable numeric value is more convenient than the categorical reason or breakdown views. - [Get chain capabilities](https://readme.cipherowl.ai/reference/riskreasonservice_getchaincapabilities.md): Returns, for every supported chain, which CipherOwl capability tiers are available. The tiers are progressive: `screening` is the baseline address-screening capability; `reporting` means the full Screening, Risk & Reporting (SRR) API stack is available; `research` means the chain is also available in the OwlTrace research experience (graph exploration, transaction explorer, and related investigative tooling). - [Get risk assessment report](https://readme.cipherowl.ai/reference/risk_assessment_api-1.md): Generates a human-readable risk-assessment report for an address, synthesizing its screening result and risk reasons into an analyst-ready narrative with supporting evidence. Use it to produce compliance documentation without manually assembling the underlying screen, reason, and breakdown data. - [Get risk flow graph](https://readme.cipherowl.ai/reference/graph_api-1.md): Returns a risk-flow diagram for an address that visualizes how funds move between it and the risky entities it is exposed to. The diagram is available as Mermaid markup, an interactive HTML wrapper, or a rendered PNG image, making it suitable for embedding in reports or investigation UIs. - [Get SAR report](https://readme.cipherowl.ai/reference/sar_report_api-1.md): Generates a draft Suspicious Activity Report (SAR) narrative for an address, formatting its risk findings into the structure compliance teams need for regulatory filing. Use it as a starting point for a SAR submission rather than writing the narrative from scratch. - [Get balance](https://readme.cipherowl.ai/reference/onchainservice_getbalance.md): Retrieves native currency balance and token holdings for a single blockchain address. Token balances are automatically included for chains that support them (Ethereum, Solana, XRP, Avalanche, etc.). - [Batch get balances](https://readme.cipherowl.ai/reference/onchainservice_batchgetbalance.md): Retrieves balance information for up to 100 addresses on the same blockchain in a single efficient request. Partial failures are supported - if some addresses fail, successful results are still returned with error details for failed addresses. - [List chains](https://readme.cipherowl.ai/reference/onchainservice_getsupportedchains.md): Returns metadata for all blockchain networks supported by this service, including chain identifiers, names, native units, and token support capabilities.