iDenfy Identity Verification API

Name: iDenfy Identity Verification API
Brand: iDenfy Identity Verification API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthIdentity VerificationapiKey1 EndpointsREST

For Agents

Create iDenfy verification sessions that drive document and biometric identity checks for KYC onboarding flows.

Install Jentic One Beta

Connect the iDenfy Identity Verification API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the iDenfy Identity Verification 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 iDenfy Identity Verification API.

Create a verification session token tied to a specific client identifier via POST /token

Configure session-level options for document type, locale, and callback URL at session creation

Hand off the returned token to the iDenfy front-end SDK so the user completes document capture

GET STARTED

Start building with iDenfy Identity Verification API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for iDenfy Identity Verification API, keeping it validated and agent-ready. iDenfy is a Lithuanian KYC and identity verification platform offering document verification, biometric face matching, and AML screening. The /token endpoint creates a verification session for a client, returning an authentication token that the front-end SDK uses to walk the user through document capture and selfie matching. Verification results are delivered via callback to the integrator and queryable through the dashboard.

Use Cases

Patterns agents use iDenfy Identity Verification API for, with concrete tasks.

★ Regulated Account Onboarding

A regulated platform — neobank, broker, crypto exchange — onboards a new customer by creating an iDenfy verification session via POST /token. The customer completes document capture and a selfie in the iDenfy SDK, and the backend receives a verification verdict via callback. Most integrations are live within 1-2 days because the session-token model removes the need to host any document handling in the integrator's stack.

Call POST /token with the client ID and locale, then return the token to the front-end SDK and wait for the verification callback

Marketplace Seller Verification

A marketplace requires sellers to complete identity verification before listing high-value items. The agent creates an iDenfy session for the seller through /token and gates listing creation behind a successful callback. This protects the marketplace from fraudulent sellers without requiring buyers to verify too.

Call POST /token with the seller's client ID and a callback URL pointing to the marketplace's listing-gating service

Age and Document Type Restricted Sign-Up

When a service is restricted by age or document type — for example only government-issued IDs from specific countries — the integrator passes the constraint at session creation and iDenfy's flow enforces it. The verification verdict returned via callback indicates whether the constraint was satisfied.

Call POST /token with allowedDocumentTypes restricted to passport and the user's expected country, then act on the callback verdict

AI Agent Compliance Onboarding

A compliance agent uses Jentic to find iDenfy operations matching 'verify a new customer for KYC', loads the /token schema, and creates a verification session for each new sign-up. The agent returns the SDK-ready token to the front-end and listens for the callback to advance the user's onboarding state.

Use Jentic search 'verify a new customer for KYC' to load the iDenfy /token schema and execute it with the new user's client ID

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for idenfy identity verification api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/token

Create a verification session token tied to a client identifier

POST

/token

Create a verification session token tied to a client identifier

Why Jentic?

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

Credential isolation

iDenfy API keys are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped execution access — the Authorization header is injected at call time and the raw key never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'verify a new customer for KYC') and Jentic returns the iDenfy /token operation with its input schema, so the agent can create a session without reading the dashboard documentation first.

Time to first call

Direct iDenfy integration: 2-4 days for backend session creation, callback handling, and front-end SDK integration. Through Jentic: under 1 hour for the backend call layer — search, load schema, execute (the front-end SDK and callback wiring remain a separate step).

FAQs

Specific to using iDenfy Identity Verification API through Jentic.

Why is there no official OpenAPI spec for iDenfy Identity Verification API?

iDenfy does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call iDenfy Identity Verification API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the iDenfy Identity Verification API use?

The iDenfy API uses an API key passed in the Authorization header. Keys are issued from the iDenfy dashboard and are tied to a merchant account. Through Jentic, the key is stored encrypted in the MAXsystem vault and injected at execution time, so it never enters the agent's prompt context.

Can the iDenfy API perform biometric face matching?

Yes. The verification session created via POST /token can include a selfie step that matches the user's live face against the photo on the verified document. The matching result is delivered to the integrator via the configured callback URL after the user completes the SDK flow.

What are the rate limits for the iDenfy Identity Verification API?

iDenfy applies per-account rate limits and a monthly verification quota tied to the merchant agreement. The OpenAPI spec does not encode hard thresholds. Design agents to handle 429 responses with backoff and to create one session token per user rather than reusing tokens across users.

How do I create a verification session through Jentic?

Run pip install jentic and import the SDK, then await client.search('verify a new customer for KYC') to find the iDenfy /token operation. Load the schema and execute with the client ID and locale, then pass the returned token to the iDenfy front-end SDK. Sign up at https://app.jentic.com/sign-up for an API key.

Where is the verification result delivered?

Verification verdicts are not returned synchronously from /token — instead they are delivered to the callback URL configured at session creation, and are also visible in the iDenfy dashboard. Build the agent to listen for the callback and advance the user's onboarding state when it arrives.