AZ Document verification

AZAPI

Low-cost document and KYC verification API that runs inside Zenoo onboarding flows.

At a glance

Overview

AZAPI overview

AZAPI is a document and KYC verification API positioned as a low-cost option with a simple RESTful interface. It suits early-stage and cost-sensitive teams building document checks into an onboarding flow. For US and EU coverage it is best paired with a second provider and a manual review fallback.

Company
AZAPI
Category
Document verification
Strongest in
Low-cost, fast document checks
Best fit
Cost-sensitive, early-stage document verification

Where it is strongest

Key strengths

What AZAPI does well.

01

Low per-check pricing

Some reports cite pricing well below many enterprise document providers for basic KYC checks.

02

Fast, simple API

Community reports describe quick response times and a straightforward RESTful API with usable initial documentation.

03

Reliable for basic operations

Some reports cite solid uptime for standard verification calls.

Who it suits

Best for

Where AZAPI fits, and what to plan for.

Honest notes on the trade-offs, each with a way to cover the gap inside a Zenoo flow.

Best for
  • Cost-sensitive startups building document verification into an early onboarding flow
  • Prototype and MVP KYC where a manual review fallback is in place
Considerations
  • Document coverage outside US and EU. Some reports suggest weaker coverage for non-US and non-EU documents, so route those regions through a second provider in your Zenoo flow.
  • Webhook reliability. Community reports cite dropped webhook events, which Zenoo mitigates through its own event handling and fallback routing across providers.
  • Support responsiveness. Some reports describe email-only support with slower turnaround, so keep a fallback verification step live and rely on Zenoo's single support path across your stack.
You

Open the customer's case

What your team sees

The AZAPI result, beside everything else.

The result sits with screening and review on one case, so nobody checks a second tool to see the whole customer.

LA
Lorraine AshcombeSample case · Personal
In review
AZAPIVerified
Name and date of birthAgrees
PEP screeningSuggested
Name matches a list entry, but the date of birth differs. Suggest you clear as a false positive.Zenoo suggests, your team decides
You

Tomorrow, your case

Bring us a case that went wrong.

We will run it through Zenoo while you watch: the evidence, the decision, and the record your MLRO would want to defend.

30 minutes. Your data. No slides.