Evaluation
Test the API with your own data.
The integration environment runs the same engine and protocol as production. It is not a demo or simulation — it executes real screening logic against reference data so you can validate your integration before going live.
What you can try.
Batch screening accuracy
Submit a known entity list and compare resolution results against expected outcomes. Inspect which layer resolved each entity and the confidence basis.
Layer distribution analysis
Review how entities distribute across L1 (deterministic), L2 (vector), L3 (semantic), and L4 (human review). Understand cost implications per layer.
Evidence completeness
Examine the DecisionEventPackage for representative entities. Verify that lineage, rule bindings, data bindings, and configuration snapshots are present.
Integration patterns
Test API endpoints with your existing tooling. Validate request/response schemas, error handling, and webhook delivery.
Audit report format
Generate a sample audit report and review the regulatory narrative format. Confirm the evidence chain meets your reporting requirements.
Limits and safety.
The evaluation environment has defined boundaries. Evaluation access does not grant production API keys, production data, or system configuration access.
For the complete reliance model, review the evaluation boundaries.
| Constraint | Limit |
|---|---|
| Batch size | Up to 1,000 entities per submission |
| L3 budget | Capped per evaluation tenant |
| Data scope | Reference watchlist data (not production feeds) |
| Retention | Evaluation data retained for 30 days |
| Tenant isolation | Evaluation tenants fully isolated from production |
| Reliance | Sandbox results are screening signals for testing, not final compliance determinations |
Request access.
There is no sales process required to begin evaluation. Access is granted based on use case fit.
- 1.Submit a request with your organization, use case, and estimated screening volume.
- 2.Receive evaluation access details after review.
- 3.Submit test data, inspect results, validate integration patterns.
- 4.Export evidence samples and audit reports for internal review.
- 5.Proceed to production onboarding or schedule a technical discussion.
Ready to integrate.
Request API access. We'll follow up after reviewing your integration use case.