Prembly API

Name: Prembly API
Brand: Prembly API
Availability: InStock

✓ Official Vendor SpecIdentity AuthIdentity VerificationapiKey32 EndpointsREST

For Agents

Verify identities with document checks, biometric face matching, liveness detection, and PEP/sanctions screening across African and emerging markets.

Install Jentic One Beta

Connect the Prembly API to your agent

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

Verify government-issued identity documents with face comparison in a single call

Screen individuals against global PEP and sanctions watchlists

Detect facial liveness to prevent spoofing during biometric onboarding

GET STARTED

Start building with Prembly API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Prembly API for, with concrete tasks.

★ Customer Onboarding KYC

Verify new customer identities during account registration using government-issued ID documents combined with biometric face matching. Prembly processes the document image, extracts data fields, compares the document photo against a live selfie, and returns a verification verdict. This covers markets across Africa where traditional credit bureau checks are unavailable, enabling fintech and banking products to onboard users in minutes rather than days.

Submit a Nigerian national ID card image and a selfie to the document-verification-face endpoint and confirm the verification status is approved

PEP and Sanctions Screening

Screen individuals and entities against politically exposed persons lists and international sanctions databases before processing transactions or establishing business relationships. The Prembly PEP/sanctions endpoint accepts a person's name and returns matching records with confidence scores, enabling compliance teams to make informed decisions. Screening runs in real time and supports ongoing monitoring for changes in status.

Submit a full name to the pep-sanction endpoint and parse the response to determine if any matches exceed a 0.8 confidence threshold

Employee Background Checks

Conduct pre-employment background verification by creating candidates, attaching verification packages, and tracking results through completion. Prembly supports configurable packages that can include ID verification, criminal record checks, and education verification. The candidate lifecycle tracks from submission through completion with status polling or reinitiation if additional information is needed.

Create a new candidate with personal details, assign a standard verification package, and poll the candidate status until verification completes

AI Agent Identity Verification Pipeline

AI agents use Prembly through Jentic to build automated identity verification pipelines that combine document scanning, face comparison, and liveness detection without manual integration work. The agent searches Jentic for identity verification operations, loads the required schemas, and executes multi-step verification flows including document upload, biometric matching, and status checking in a single orchestrated sequence.

Search Jentic for 'verify identity document with face match', load the document-verification-face operation schema, and execute with a test document image and selfie

Key Endpoints

32 endpoints — prembly provides identity verification and fraud prevention services focused on emerging markets across africa and beyond.

METHOD

PATH

DESCRIPTION

POST

/document-verification

Verify an identity document

POST

/document-verification-face

Verify document with face comparison

POST

/face-liveliness

Detect liveness in a facial image

POST

/pep-sanction

Screen against PEP and sanctions lists

POST

/face-comparison

Compare two facial images

POST

/candidates

Create a background check candidate

GET

/verification-status

Check status of a verification request

POST

/tm-transaction-monitoring

Monitor a transaction for fraud

POST

/document-verification

Verify an identity document

POST

/document-verification-face

Verify document with face comparison

POST

/face-liveliness

Detect liveness in a facial image

POST

/pep-sanction

Screen against PEP and sanctions lists

POST

/face-comparison

Compare two facial images

Why Jentic?

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

Credential isolation

Prembly API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens with the Authorization header pre-configured, so the raw secret key never enters the agent context.

Intent-based discovery

Agents search by intent (e.g., 'verify identity document with face match') and Jentic returns matching Prembly operations with their input schemas including required image formats and country codes.

Time to first call

Direct Prembly integration: 2-4 days for auth setup, document handling, and response parsing. Through Jentic: under 1 hour — search for verification operations, load schemas, and execute.

FAQs

Specific to using Prembly API through Jentic.

What authentication does the Prembly API use?

The Prembly API uses API key authentication passed in the Authorization header. Through Jentic, your API key is stored encrypted in the MAXsystem vault and agents receive scoped access tokens, so the raw secret key never enters the agent context.

Can I verify identity documents with face matching in a single request?

Yes. The POST /document-verification-face endpoint accepts both an identity document image and a selfie, performs document data extraction and facial comparison together, and returns a combined verification result with confidence scores.

What are the rate limits for the Prembly API?

Rate limits depend on your Prembly subscription tier. You can check your current usage capacity via the GET /wallet-balance endpoint which returns your remaining verification credits. Higher-tier plans include increased throughput and priority processing.

How do I run a PEP and sanctions screening through Jentic?

Search Jentic for 'screen person against sanctions list', load the pep-sanction operation schema, and execute with the person's full name. The response includes matched records with confidence scores. Install the SDK with pip install jentic and authenticate with your JENTIC_AGENT_API_KEY.

Which countries does the Prembly API support for identity verification?

The GET /countries endpoint returns the full list of supported countries. Prembly focuses on African and emerging markets including Nigeria, Kenya, Ghana, South Africa, and others, with document types varying by country. The GET /check-types endpoint lists available verification methods per country.

Can I track the status of an ongoing background check?

Yes. After creating a candidate via POST /candidates, poll GET /candidates/{id} to check the verification progress. If a check stalls or needs re-submission, use POST /candidates/{id}/reinitiate to restart the process with updated information.

Prembly API

Connect the Prembly API to your agent

Capabilities

Start building with Prembly API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs