Developer
API-first screening infrastructure.
CCAI is designed for programmatic consumption. Platform teams integrate screening into existing workflows without adopting a standalone product.
API Endpoints
Authentication via API key. Tenant context bound via request header. All responses include trace identifiers for audit correlation.
| Method | Endpoint | Description |
|---|---|---|
| POST | /resolve | Screen a single entity |
| POST | /batch | Submit a batch of entities (JSON array) |
| POST | /batch-upload | Upload a file for batch screening (multipart) |
| GET | /audit/{trace_id} | Retrieve full audit trail for a screening |
| GET | /health | System health with component status |
| GET | /stats | Global performance metrics |
Batch Screening
Batch processing is the primary operational mode for most integrations. Batches support up to 10,000 entities per submission, parallelized across resolution layers.
- 1.Submit entity file (CSV, XLSX, JSON, Parquet) or JSON array
- 2.Receive batch_id and trace_id in the response
- 3.Poll for completion or receive webhook notification
- 4.Retrieve results with per-entity resolution detail
- 5.Export evidence bundles or audit reports as needed
Event and Webhook Model
CCAI emits events at key points in the screening lifecycle. Webhooks are delivered via HTTP POST with signed payloads. Events include trace_id and batch_id for correlation.
| Event | Trigger |
|---|---|
| batch.completed | All entities in a batch have been resolved |
| batch.failed | Batch processing encountered an unrecoverable error |
| alert.created | A new case has been escalated to human review |
| monitoring.delta | A monitored entity’s status changed on re-screen |
Evaluation Workspace
Before production integration, teams can evaluate CCAI in a sandboxed environment. Submit test batches against reference data, inspect resolution results and evidence output, and validate API integration patterns.
The evaluation workspace uses the same engine and protocol as production. The only difference is the data scope and access tier.
CCAI as a screening layer
CCAI is infrastructure, not a product you switch to. It fits into existing compliance architectures.
For platform teams
Embed screening as an API call within existing entity onboarding, transaction monitoring, or KYC workflows. CCAI handles resolution and evidence generation. Your platform handles the business logic.
For compliance systems
Feed CCAI the entity lists your existing systems produce. Consume the structured evidence output for regulatory reporting. CCAI does not replace your compliance program — it provides the screening execution and evidence layer.
For data pipelines
Submit batch files on a schedule. Receive structured results with full lineage. Load results into your data warehouse or reporting system. CCAI operates as a processing stage, not a destination.
Get API access.
Request evaluation credentials to test the API against your integration requirements.