Product

Compliance infrastructure for modern organizations.

eupeak.io is a middleware API that sits between your application or internal tool and the world’s compliance data sources. It normalizes, deduplicates, and scores data from sanctions lists, PEP databases, and adverse media — and returns a single structured response you can act on.

Architecture

Five layers. One response.

Layer 1 · Gateway

API Gateway

api.eupeak.io — authentication, rate limiting, audit logging and versioning. Every request is logged with source, timestamp, latency and result.

Layer 2 · Fan-out

Aggregation Engine

Fans out to all configured sources in parallel using Promise.allSettled — meaning a single slow or unavailable source never degrades your response time. Results are deduplicated using fuzzy entity matching (Jaro-Winkler distance) and scored by match confidence.

Layer 3 · Scoring

Risk Scoring Engine

Assigns a 0–100 risk score based on match type weights: sanctions (60 pts), PEP (40 pts), watchlist (30 pts), adverse media (20 pts) — plus a multi-source confirmation bonus. Returns risk_level: low / medium / high / critical.

Layer 4 · Cache

Redis Cache Layer

Entity screenings cached for 6 hours (1 hour for persons). Reduces cost and improves response time for repeat queries. Cache status always visible in the response payload.

Layer 5 · Delivery

Webhook Delivery

Configure webhooks to receive push notifications when a screening completes with flags or a monitored entity receives a new match.

Response anatomy

Every /v1/screen response includes.

id: UUID — for retrieving the screening later
entity: The normalized query string
risk_score: 0–100 composite score
risk_level: low / medium / high / critical
flags[]: Each match: type, source, list, match_score, details
sources_queried: All sources contacted
sources_matched: Sources that returned at least one match
cache_hit: Whether the result was served from cache
duration_ms: End-to-end response time
timestamp: ISO 8601

Security & data handling

Defensible by design.

Transport & storage

All API traffic encrypted in transit (TLS 1.3)
API keys stored as SHA-256 hashes — never plaintext
Screening payloads stored on EU-region infrastructure

Tenancy & retention

Row Level Security enforced at database level
Audit log is append-only and cannot be modified
No screening data shared across tenant accounts
Data retention: 24 months, then purged

Get started → Read the docs