COVALENT
Developers

Compliance infrastructure exposed as APIs.

Submit transfers, screen wallets, receive webhooks, and automate reporting workflows without implementing Travel Rule protocols or jurisdiction logic yourself.

View API docs Get started

REST API

Submit transfers, register wallets, search VASPs, and read compliance state through API endpoints.

Webhooks

Receive events for transfers, cases, screening, reports, and other compliance workflows, with retry history.

Scoped Environment

Use separate Test and Live keys with scope based access, rate limits, rotation, revocation, and usage tracking.

Test / Live split

Separate providers, rules, customers, webhooks, and transfers before production traffic moves.

API-first

One request can return the compliance decision.

Covalent packages risk, sanctions, Travel Rule obligations, and filing thresholds into one response that product systems can act on.

Request 
POST /v2/transfers/screen
Authorization: Bearer covalent_live_...

{
  "wallet": "0x8f34...91b2",
  "jurisdiction": "SG",
  "amount": 12000,
  "asset": "USDC"
}
Response 
{
  "risk_score": 82,
  "sanctions_hits": 0,
  "travel_rule": "required",
  "filing_threshold": "str_review",
  "decision": "review"
}
Webhook lifecycle

Build around state changes, not polling loops.

transfer.created

Initial transfer accepted by API

screening.complete

Provider results and risk score recorded

case.created

Rules engine opened analyst review

report.generated

STR / SAR draft produced from evidence

transfer.completed

Final lifecycle event delivered

operating system layer

Wire compliance into your product surface.

Start with sandbox API keys, signed webhook events, and the same workflow model used by the Covalent console.

Get started Read docs