Mitekcloud Mitek Identity Cloud API

Name: Mitek Identity Cloud API
Brand: Mitek Identity Cloud API
Availability: InStock

✓ Official Vendor SpecIdentity AuthIdentity Verificationbearer12 EndpointsREST

For Agents

Run document and biometric identity verification, extract structured data from IDs, and check faces against a blocklist via Mitek's KYC platform. Issues OAuth tokens and supports AAMVA driver licence checks.

Install Jentic One Beta

Connect the Mitek Identity Cloud API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mitek Identity Cloud API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Mitek Identity Cloud API.

Run document plus selfie identity verification with Mobile Verify

Extract structured data from photographed IDs with Mobile Fill

Enrol and verify users biometrically through MiPass

GET STARTED

Start building with Mitek Identity Cloud API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Mitek Identity Cloud API for, with concrete tasks.

★ KYC Onboarding Flow

New customer signups capture a government ID and a selfie, and the Mitek API confirms the document is genuine, the face matches the photo on the document, and the data fields are consistent. The verification dossier endpoint orchestrates these checks in one call so the onboarding system gets a single pass or fail decision plus extracted personal data for account creation.

Submit a verification dossier with a passport image and selfie via POST /api/verify/v2/dossier and parse the decision and extracted fields

Returning Fraudster Detection

Maintain a blocklist of faces from confirmed fraud cases, then on every new application check the applicant's selfie against the list before any other verification step. The biometric endpoint returns a match score with metadata so the orchestrator can decline the application immediately and avoid wasting downstream verification budget.

Add the confirmed fraud applicant's face to the blocklist via POST /api/blocklist/v2/items and re-run the next applicant's selfie against it

Form Prefill from ID Photo

Reduce signup form friction by letting the user photograph their ID card, then call Mobile Fill to extract name, address, date of birth, and document number. The structured fields populate the form and the user only confirms or corrects them, cutting completion time without losing data quality.

Call POST /api/fill/v2/document with a driver licence image and map the returned fields to the user signup form

Agent-Mediated Verification via Jentic

An onboarding agent discovered through Jentic can call the dossier endpoint, branch on the verification decision, and trigger downstream actions like account creation or manual review queueing. Jentic isolates the bearer token in the credential vault so the agent never sees the raw secret used to call Mitek.

Use Jentic to find the Mitek verification dossier operation, execute it with applicant images, and route the case based on the decision field

Key Endpoints

12 endpoints — the mitek identity cloud api runs identity verification, document data extraction, biometric enrollment, and aamva driver licence checks for kyc and onboarding flows.

METHOD

PATH

DESCRIPTION

POST

/connect/token

Issue an OAuth access token

POST

/api/verify/v2/dossier

Run a full document and selfie verification

POST

/api/fill/v2/document

Extract fields from an ID image

POST

/api/biometric/v2/enrollments

Enrol a face for MiPass

POST

/api/biometric/v2/verify

Verify a selfie against an enrolment

POST

/api/blocklist/v2/items

Add a face to the fraud blocklist

POST

/connect/token

Issue an OAuth access token

POST

/api/verify/v2/dossier

Run a full document and selfie verification

POST

/api/fill/v2/document

Extract fields from an ID image

POST

/api/biometric/v2/enrollments

Enrol a face for MiPass

POST

/api/biometric/v2/verify

Verify a selfie against an enrolment

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Mitek bearer tokens and the underlying client credentials are stored encrypted in the Jentic vault. Agents receive scoped execution rights and never see the raw client_secret or access token.

Intent-based discovery

Agents search Jentic with intents like verify customer identity or run document check and Jentic returns the matching Mitek operation with input schema and example payload.

Time to first call

Direct Mitek integration: 1-2 weeks to handle token issuance, multipart image uploads, and decision parsing. Through Jentic: under 1 hour to search, load, and execute the dossier endpoint.

FAQs

Specific to using Mitek Identity Cloud API through Jentic.

What authentication does the Mitek Identity Cloud API use?

The API uses bearer token authentication. Tokens are issued from POST /connect/token using your client credentials and passed in the Authorization header on subsequent calls. Through Jentic the bearer token is held in the credential vault and injected at execution time.

Can I extract data from a driver licence with the Mitek API?

Yes. Use the Mobile Fill endpoint at POST /api/fill/v2/document, posting the licence image. The response returns extracted fields such as name, address, date of birth, and document number ready to populate a signup form.

What are the rate limits for the Mitek Identity Cloud API?

Mitek applies per-tenant request limits that depend on your contract. Verification dossier calls are typically capped at a lower rate than token issuance. Check your Mitek customer portal for the current numeric quotas before running batch backfills.

How do I run a full KYC check through Jentic?

Search Jentic for verify identity dossier, load the schema for POST /api/verify/v2/dossier, and execute with the applicant's document image and selfie. The structured response includes a decision and the extracted document fields for downstream account creation.

Does the Mitek API support biometric face matching?

Yes. The MiPass endpoints under /api/biometric/v2 enrol a user's face and then verify a new selfie against that enrolment. You can also check faces against the fraud blocklist via /api/blocklist/v2/items.

Can the Mitek API verify US driver licences against AAMVA?

Yes. The verification dossier supports AAMVA-backed checks for US driver licences as part of the verify flow. The decision response indicates whether the AAMVA component passed alongside document and biometric results.

Mitekcloud Mitek Identity Cloud API

Connect the Mitek Identity Cloud API to your agent

Capabilities

Start building with Mitek Identity Cloud API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs