Release Notes

Version 2.1.0

🚀 What's New

Unified API endpoint: All public API endpoints are now served from svc.cipherowl.ai. Point your base URL to https://svc.cipherowl.ai — request paths and payloads are unchanged.
Update (2026-10-05) — chain vs network in every URL: /chains/{chain}/… takes a chain (evm, bitcoin, tron; risk is evaluated per chain) and /networks/{network}/… takes a network (ethereum_mainnet; balances and recorded metadata live on a network). See Parameters. Two paths changed spelling and the previous spelling stays served: Continuous Monitoring's per-address risk history is now GET /api/monitoring/v1/pools/{pool_id}/chains/{chain}/addresses/{address}/risk-history, and the Onchain Service and Private Data APIs are documented under /networks/{network}/…. Onchain Service requests and responses now carry a network field; the chain field holds the same value, stays served, and is deprecated.

⚠️ Deprecation Notice

The legacy tools.prod.cipherowl.ai host is deprecated and will be retired after a transition period. During the transition both hosts return identical responses; please switch to svc.cipherowl.ai at your earliest convenience.
Update (2026-09-07): The transition period has ended and tools.prod.cipherowl.ai has been retired. The hostname no longer resolves, so requests sent to it fail at the DNS layer. Use https://svc.cipherowl.ai; request paths and payloads are unchanged.

Version 2.0.0

🚀 What's New

Introducing the new SRR (Screen, Reason, Report) API suite:

Risk Screening API
- Screen addresses for risk assessment
Risk Reasoning API
- Provide detailed risk reasoning for addresses
Risk Report API
- Generate comprehensive risk assessment reports for addresses

⚠️ Migration Notice

CipherOwl will assist all existing customers in migrating from legacy APIs to the new SRR API suite. Legacy APIs will be deprecated following the completion of migration.

Version 1.1.0

🚀 What's New

Introduced Sanctions API for checking sanctioned addresses across multiple jurisdictions
Introduced Risk Score API for evaluating address risk with directional scoring
Support for batch operations (up to 50 addresses per request)

🔒 Security Updates

OAuth 2.0 Authentication: All API requests now require OAuth 2.0 authentication. Obtain client_id and client_secret during onboarding, then request an access_token for API access.

Example - Obtaining an access token:

curl --request POST \
     --url https://svc.cipherowl.ai/oauth/token \
     --header 'Content-Type: application/json' \
     --data '{
         "client_id": "{YOUR_CLIENT_ID}",
         "client_secret": "{YOUR_CLIENT_SECRET}",
         "audience": "svc.cipherowl.ai",
         "grant_type": "client_credentials"
     }'

Example - Using the access token:

Authorization: Bearer {YOUR_ACCESS_TOKEN}

Access tokens expire after a specified period and must be refreshed
Rate limit exceeded errors return HTTP 429 status code