IDWise API

Name: IDWise API
Brand: IDWise API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthIdentity Verificationbasic13 EndpointsREST

For Agents

Run KYC and identity verification journeys with document checks, facial biometrics, proof of address, and AML screening through IDWise's hosted flow.

Install Jentic One Beta

Connect the IDWise API to your agent

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

Start a verification journey for a new applicant via POST /v2/start-journey

Process individual verification steps such as document upload and selfie capture

Generate hosted verification links to send to end users via /v2/verification-links

GET STARTED

Start building with IDWise API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for IDWise API, keeping it validated and agent-ready. IDWise provides identity verification including document authentication, facial biometrics, proof of address, and AML screening. Agents can start a verification journey, process individual journey steps, complete the journey, retrieve verification results and summaries, generate hosted verification links, and submit manual review decisions. The API also exposes audit logs and supports regional endpoints for the UAE and a QA environment.

Use Cases

Patterns agents use IDWise API for, with concrete tasks.

★ Customer KYC Onboarding

Run document and biometric KYC during onboarding for fintech, crypto, and gaming platforms. The agent calls POST /v2/start-journey to create the journey, sends a hosted verification link to the user, then polls GET /v2/get/{JOURNEY_ID} for the structured result including extracted document fields, face match score, and liveness verdict. Typical completion in minutes, with manual review fallback for ambiguous cases.

Start a journey for applicant 'user-1024', generate a hosted link, then poll /v2/get/{JOURNEY_ID} until the journey status is COMPLETED.

AML Screening with Proof of Address

Combine identity verification with AML watchlist screening and proof-of-address checks for regulated industries. IDWise runs sanctions, PEP, and adverse-media screening alongside the document check, then returns a consolidated verdict the agent can use to auto-approve, escalate, or reject the applicant.

Retrieve the journey summary via GET /v2/summary/{journey_id} and route to manual review if AML hits are present.

Manual Review Workflow

When automated checks return a borderline result, an agent or compliance officer submits a manual review decision via POST /v2/manual-review/{JOURNEY_ID}. This use case covers the queue management and decision-recording side of identity verification, with full audit trail through GET /audit-logs.

Submit a manual review decision of 'APPROVED' on a flagged journey and pull the audit log entry to confirm it was recorded.

AI Agent KYC Orchestration

An AI agent in a banking or crypto onboarding flow runs end-to-end KYC: it triggers IDWise, monitors the journey, parses the verdict, and writes the decision back to the customer record. Through Jentic, the agent discovers the right operations from a single search query without reading IDWise's docs.

Use Jentic to call POST /v2/start-journey for an applicant, wait for completion, and surface the verdict in chat.

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for idwise api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v2/start-journey

Start a new identity verification journey

POST

/v2/process-journey-step

Process an individual journey step

POST

/v2/complete-journey

Mark a journey complete

GET

/v2/get/{JOURNEY_ID}

Retrieve verification results

GET

/v2/summary/{JOURNEY_ID}

Get journey summary

POST

/v2/verification-links

Create a hosted verification link

POST

/v2/manual-review/{JOURNEY_ID}

Submit a manual review decision

GET

/audit-logs

Retrieve verification audit logs

POST

/v2/start-journey

Start a new identity verification journey

POST

/v2/process-journey-step

Process an individual journey step

POST

/v2/complete-journey

Mark a journey complete

GET

/v2/get/{JOURNEY_ID}

Retrieve verification results

GET

/v2/summary/{JOURNEY_ID}

Get journey summary

Why Jentic?

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

Credential isolation

IDWise Basic Auth credentials are stored encrypted in the Jentic vault. Agents receive scoped execution access only — the raw username and password never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'verify a customer's identity') and Jentic returns the matching IDWise journey operation with its input schema.

Time to first call

Direct IDWise integration: 3-5 days for auth, journey orchestration, and webhook handling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using IDWise API through Jentic.

Why is there no official OpenAPI spec for IDWise API?

IDWise does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call IDWise 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 IDWise API use?

IDWise uses HTTP Basic authentication. Through Jentic, the credentials are held in the vault and injected at execution time, so the agent never receives the raw username and password.

Can I run AML screening with the IDWise API?

Yes. The verification journey returned via GET /v2/get/{JOURNEY_ID} includes AML screening output alongside document and biometric checks, configurable per applicant.

How do I generate a hosted verification link for a user?

Call POST /v2/verification-links with the journey configuration. IDWise returns a URL you send to the end user; their results flow back into the journey, retrievable by GET /v2/summary/{JOURNEY_ID}.

What are the rate limits for the IDWise API?

The OpenAPI spec does not declare explicit rate limits. IDWise enforces account-tier throttles agreed in the contract; handle 429 responses with exponential backoff.

How do I run a KYC journey through Jentic?

Run pip install jentic, then search 'verify a customer's identity', load the schema for POST /v2/start-journey, and execute with the applicant details. Poll GET /v2/get/{JOURNEY_ID} for the verdict.

IDWise API

Connect the IDWise API to your agent

Capabilities

Start building with IDWise API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs