Frankie Financial API

Name: Frankie Financial API API
Brand: Frankie Financial API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthIdentity VerificationapiKey46 EndpointsREST

For Agents

Run KYC, KYB, AML, and document verification checks for Australian and international entities, including PEP, sanctions, and watchlist screening. Authentication is an api_key header.

Connect the Frankie Financial API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Frankie Financial API API.

Verify an individual's name, address, and date of birth against national databases

Scan and validate Australian driver's licences, passports, Medicare cards, and visas

Run PEP, sanctions, watchlist, and adverse-media screening on an entity

Query organisation ownership and run KYC checks on shareholders and beneficial owners

GET STARTED

Start building with Frankie Financial API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Frankie Financial API, keeping it validated and agent-ready.

Frankie Financial is a KYC, KYB, and AML compliance utility used by Australian and New Zealand banks, fintechs, and insurers to onboard customers and businesses. The API exposes 46 endpoints across entity verification, document scanning and comparison, business ownership lookups, PEP and sanctions screening, fraud blacklists, and selfie checks. It validates Australian driver's licences, passports, Medicare cards, electricity bills, NZ driver's licences, Chinese bank cards, and a range of international identity documents.

Use Cases

Patterns agents use Frankie Financial API API for, with concrete tasks.

★ Australian Bank Account Onboarding

An Australian neobank verifies new customers in under a minute by submitting name, date of birth, and address through Frankie Financial's entity verification, then scanning a driver's licence and running a selfie comparison. The API consolidates results from multiple national databases and returns a single pass/fail decision plus the underlying check evidence for audit.

POST to /entity with the customer's name, DOB, and address, then POST /document/new/scan with the licence image and run /document/{documentId}/compare against the selfie

KYB and Beneficial Ownership

A business lender runs KYB on a corporate borrower by querying ownership through Frankie Financial, then runs KYC and AML screening on every director and beneficial owner above a 25% threshold. The API surfaces the ownership graph, credit reports, and any PEP or sanctions hits in a single workflow.

POST /business/ownership/query with the ABN, then for each beneficial owner POST /entity/new/verify with the appropriate checkType to run AML screening

Document and Selfie Verification

A digital insurer asks the customer to photograph their licence and take a selfie. Frankie Financial scans the document, extracts the fields, validates against the issuing authority, and compares the selfie against the document photo to confirm the holder is present. The full check completes asynchronously and resolves in seconds.

POST /document/new/scan with the licence image, then POST /document/new/compare with the selfie image and check the comparison verdict

AI Agent Compliance Workflow

A compliance agent triages onboarding events from a fintech queue. For each new applicant, the agent uses Jentic to call Frankie Financial's entity, document, and AML endpoints, summarises the verdicts in plain language, and routes high-risk cases to a human reviewer. The api_key never enters the agent's context.

Search Jentic for 'run a KYC check on an Australian customer', load the entity verification schema, execute against the new applicant, and post a summary back to the queue

Key Endpoints

46 endpoints — frankie financial is a kyc, kyb, and aml compliance utility used by australian and new zealand banks, fintechs, and insurers to onboard customers and businesses.

METHOD

PATH

DESCRIPTION

POST

/entity

Create an entity and start identity verification

POST

/entity/new/verify/{checkType}/{resultLevel}

Run a typed verification check on a new entity

POST

/document/new/scan

Scan and extract fields from an identity document

POST

/document/new/compare

Compare a selfie against a scanned document

POST

/business/ownership/query

Query beneficial ownership for a business

GET

/entity/{entityId}/checks

Retrieve all checks run against an entity

POST

/entity/{entityId}/flag/blacklist

Flag an entity to the shared blacklist

POST

/entity

Create an entity and start identity verification

POST

/entity/new/verify/{checkType}/{resultLevel}

Run a typed verification check on a new entity

POST

/document/new/scan

Scan and extract fields from an identity document

POST

/document/new/compare

Compare a selfie against a scanned document

POST

/business/ownership/query

Query beneficial ownership for a business

Why though Jentic?

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

Credential isolation

The Frankie Financial api_key header value is stored encrypted in the Jentic vault. Agents receive a scoped execution token, so the key cannot be leaked through prompt injection or transcript logging.

Intent-based discovery

Agents call Jentic search with intents like 'verify an Australian driver's licence' or 'run AML screening' and Jentic returns the matching Frankie operations with their input schemas, so the agent can run the right check without parsing 46 endpoints.

Time to first call

Direct Frankie Financial integration: 2-4 weeks plus the commercial onboarding period. Through Jentic: under 1 hour for the technical wiring once the customer ID and api_key are in the vault.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

ComplyAdvantage

ComplyAdvantage focuses on AML, sanctions, and adverse-media screening with a global remit

Choose ComplyAdvantage for global AML coverage; choose Frankie Financial when the workflow is centred on Australia and New Zealand identity documents.

Alternative

Onfido

Onfido provides global document and biometric verification with strong selfie liveness

Choose Onfido for global passports and selfie liveness; choose Frankie when you specifically need Australian licence, Medicare, and electricity-bill checks.

Complementary

Sumsub

Sumsub offers a configurable orchestration layer that can call Frankie checks alongside other providers

Use Sumsub as the orchestrator when a workflow needs Frankie for AU and a different provider for other regions.

Complementary

Experian

Experian provides credit data that complements Frankie's identity and AML checks

Layer Experian credit checks on top of Frankie's identity verification when the use case is lending or credit-card issuance.

FAQs

Specific to using Frankie Financial API API through Jentic.

What authentication does the Frankie Financial API use?

Frankie Financial uses an API key passed in the api_key header. Production access also requires a signed commercial agreement and a customer ID. Through Jentic, the api_key is stored encrypted in the vault and replaced with a scoped execution token before the agent runs.

Can I verify an Australian driver's licence with the Frankie Financial API?

Yes. POST the licence image or details to /document/new/scan to extract and validate the fields, then call /document/{documentId}/verify to confirm the licence against the issuing authority's database. The verification verdict and underlying evidence are returned for audit.

What are the rate limits for the Frankie Financial API?

Frankie Financial does not publish public rate limits in its OpenAPI spec. Production limits are negotiated as part of the commercial agreement and typically range from a few requests per second on standard plans up to bulk batch volumes for enterprise customers.

How do I run a beneficial ownership check through Jentic?

Search Jentic for 'beneficial ownership lookup', load the Frankie Financial /business/ownership/query schema, and execute it with the company identifier (ABN for Australia, registration number for international). Then loop the returned owners through /entity/new/verify for KYC and AML screening.

Is the Frankie Financial API free?

Frankie Financial does not offer a free production tier. A sandbox at api.demo.frankiefinancial.io is available with canned data once initial commercial discussions begin, and production pricing is per-check across the KYC, KYB, AML, and document modules.

How do I screen a customer against PEP and sanctions lists?

Create the entity at /entity, then POST /entity/new/verify/{checkType}/{resultLevel} with checkType set to the AML or watchlist option. The response returns a list of any hits along with the source list and the matched record so the compliance officer can disposition the case.