ComplyCube KYC and AML Compliance REST API
ComplyCube KYC and AML compliance REST API for fintechs, banks, crypto exchanges, and regulated businesses to automate customer identity verification, document checks, sanctions screening, PEP checks, adverse media monitoring, and ongoing compliance — enabling automated FATF-compliant KYC/AML workflows through ComplyCube's global compliance platform covering 10,000+ identity document types across 220+ countries. Enables AI agents to manage identity check for document verification and face match automation, handle AML screening for sanctions and watchlist screening automation, access PEP check for politically exposed person identification automation, retrieve adverse media for negative news monitoring automation, manage proof of address for utility and bank statement verification automation, handle extensive screening for global watchlist comprehensive check automation, access company check for KYB corporate entity verification automation, retrieve ongoing monitoring for continuous AML alert automation, manage risk score for client risk rating automation, and integrate ComplyCube with onboarding, account management, and compliance reporting platforms for end-to-end KYC/AML automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
KYC/AML. FATF, GDPR, FCA. API key. UK/EU. Identity, biometric, and AML data.
⚡ Reliability
Best When
A fintech, bank, crypto exchange, or regulated business wanting AI agents to automate KYC document verification, AML sanctions screening, PEP checks, adverse media monitoring, and ongoing compliance through ComplyCube's FATF-compliant global compliance platform.
Avoid When
JURISDICTION-SPECIFIC REQUIREMENTS VARY: KYC/AML requirements differ by jurisdiction (FATF recommendations vs. local laws); automated uniform-global-KYC assumption creates compliance_gap for jurisdiction-specific requirements; automated must implement jurisdiction-specific compliance flows. SANCTIONS LIST COVERAGE VARIES: ComplyCube screens against major sanctions lists (OFAC, EU, UN); automated all-jurisdictions-covered assumption creates missing_local_list for country-specific sanctions lists; automated must verify sanctions list coverage for specific jurisdictions. ONGOING MONITORING IS ACTIVE PROCESS: AML ongoing monitoring generates alerts that require human review; automated fully automated compliance decision assumption creates compliance_risk from unreviewed alerts; automated must implement human review workflow for compliance officer review. BIOMETRIC CONSENT REQUIRED: Face match and biometric verification requires explicit user consent in many jurisdictions; automated consent-free biometric assumption creates GDPR/BIPA violation; automated must implement proper biometric consent flow.
Use Cases
- • Automating document KYC and biometric verification for crypto exchange account opening automation agents
- • Performing sanctions and PEP screening for regulated financial services onboarding automation agents
- • Monitoring ongoing AML compliance alerts for existing customer portfolio risk management automation agents
- • Integrating KYB company verification with individual KYC for fintech B2B onboarding automation agents
Not For
- • Non-regulated businesses without compliance requirements (ComplyCube is specifically for regulatory compliance)
- • Internal employee background checks (ComplyCube is customer-facing KYC/AML, not HR screening)
- • Real estate or physical asset verification (ComplyCube is identity and entity compliance, not asset verification)
Interface
Authentication
ComplyCube uses API key for KYC/AML REST API. REST API with JSON. London, UK HQ. Founded 2017. Products: Identity verification, AML screening, PEP checks, adverse media, ongoing monitoring, company checks. SDKs: JS, Python, Ruby, PHP, Android, iOS. 10,000+ document types. 220+ countries. FCA and CBN regulated product. Backed by investors. Competes with Sumsub and Onfido for global KYC compliance platform.
Pricing
London UK. Per-check PAYG. Free trial. 10,000+ document types. Global KYC/AML platform.
Agent Metadata
Known Gotchas
- ⚠ CLIENT MUST BE CREATED FIRST: ComplyCube workflow requires creating a Client entity before running checks; automated direct-check assumption creates client_not_found; automated must create Client before creating Document, Check, or Screening resources
- ⚠ CHECKS ARE ASYNC: ComplyCube identity checks (document, biometric, AML) run asynchronously; automated synchronous result assumption creates pending_status; automated must implement webhook handler for check.completed events or poll check status
- ⚠ DOCUMENT UPLOAD PRECEDES CHECKS: Document images must be uploaded as Document resources before running identity checks; automated one-step check assumption creates no_document_found; automated must implement upload → check sequencing
- ⚠ AML ALERTS REQUIRE DISPOSITION: AML screening alerts require compliance team disposition (true positive, false positive); automated automated-screening-resolution assumption creates compliance_audit_failure; automated must route AML alerts to human compliance review
- ⚠ SDK HANDLES UI COMPLEXITY: ComplyCube web/mobile SDKs handle camera capture and document guidance; automated API-only document capture assumption creates lower_image_quality from manual capture; automated should use ComplyCube SDK for end-user document capture
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for ComplyCube KYC and AML Compliance REST API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.