Korala
Identity, fraud and agreements · API-first

Verify people and businesses. Catch fraud. Sign the agreement.

Korala reads identity documents and proofs of address, catches fraud across sessions and seals the signature when an agreement follows. You get one API, an audit trail for each decision and an MCP server for your AI assistant.

Start in the sandboxBuild with the API

Onboarding customers or businesses? See how verification works →
Have a form to fill in? Try the free chat demo →

  • Verify people
  • Verify businesses
  • Catch fraud
  • Sign & seal
Modules

One engine.
Every module.

Identity, business and fraud checks, human review and the signed agreement run as modules on one engine, and each keeps its own audit trail. Live modules ship today. We add the rest once we have measured them.

Korala engine
Korala engine
IdentityBusiness and screeningFraud and riskReview and agreement
  • Identity documentsKYC, Live
  • Proof of addressAddress evidence, Live
  • Selfie and livenessFace match, In development
  • Business checksYour KYB requirements, In development
  • Sanctions and PEPScreening, Planned
  • Wallet screeningCrypto, Planned
  • Risk scoringAcross every case, Live
  • Repeat applicantsSame document or network, Live
  • Network signalsTor, hosting, IP country, Live
  • Device integrityAutomation, virtual cameras, In development
  • Transaction monitoringAfter onboarding, Planned
  • Human reviewCases with evidence, Live
  • Signing and sealingThe agreement at the end, Live
  • Identity documentsIdentity · Live
  • Proof of addressIdentity · Live
  • Selfie and livenessIdentity · In development
  • Business checksBusiness and screening · In development
  • Sanctions and PEPBusiness and screening · Planned
  • Wallet screeningBusiness and screening · Planned
  • Risk scoringFraud and risk · Live
  • Repeat applicantsFraud and risk · Live
  • Network signalsFraud and risk · Live
  • Device integrityFraud and risk · In development
  • Transaction monitoringFraud and risk · Planned
  • Human reviewReview and agreement · Live
  • Signing and sealingReview and agreement · Live
LiveIn developmentPlanned Status on 8 October 2026. Live modules ship today. We make no claims yet for In development or Planned modules.
How it works

From documents to a decision,
in the steps you choose.

Each applicant goes through the same steps. They upload their documents, Korala reads them, runs the checks you switched on and compares the case with earlier ones, and a person decides the hard ones. One run is a session. Pick an example flow to see which steps and modules it uses.

Example flow
Module status todayLiveIn developmentPlanned

The applicant providesID document, proof of address, selfie

  1. 01 / CaptureCollect the documents

    The applicant uploads what the flow asks for: an ID, a proof of address, company papers. In Korala, through a link on any device.

  2. 02 / ExtractRead the documents

    Korala reads each document and keeps a fingerprint of the file, its text and its details, so it recognises the same document if it turns up again.

    • Modules
    • Passports and ID cardsLive
    • Proof of addressLive
    • Company documentsIn development
    • Right-to-work evidencePlanned
  3. 03 / CheckRun the checks you switched on

    Each check is a module. Turn it on in the configuration and it runs here, on the documents from step two.

    This example is
    at this step
    • Modules
    • Expiry and format rulesLive
    • Selfie matches the IDIn development
    • Network signalsLive
    • Device integrityIn development
    • Sanctions screeningPlanned
    • Company registry lookupPlanned
  4. 04 / RiskCompare with every earlier case

    Some fraud only shows across cases: the same document under another name, many accounts from one network, too many attempts too fast.

    • Modules
    • Same document seen beforeLive
    • Same person, many accountsLive
    • Too many attempts, too fastLive
    • Many applicants from one networkLive
    • Sanctioned wallet addressesPlanned
  5. 05 / ReviewHand hard cases to a person

    Low risk can pass on its own. Medium and high risk wait for a reviewer, with every document and flag attached.

    • Modules
    • AI investigation briefLive · opt-in
  6. 06 / Sign & sealSign the agreement, if there is one

    Korala fills your template with the verified details, collects the signature and seals it so any later change shows.

    Optional step · the link from session to signature is in design
  7. 07 / MonitorKeep watching afterwards

    Your app sends logins, payments and transfers as they happen. Korala answers allow, review or block.

    Planned

You receiveDecision · signed account agreement · audit trail · webhook

Live, In development and Planned describe each module today, not this example. The selected flow skips the dimmed steps and modules. Status as of 8 October 2026.

Explore fraud and risk →
AI-native

No workflow builder to learn.
Ask your assistant to set it up.

Describe the flow in plain words, and your assistant connects to Korala through MCP with the permissions you grant. Today it prepares and sends documents. Soon it will also set up verification workflows and risk policies, test them in the sandbox and hand you a link to review.

AssistantKorala connected · sandbox · sending off
Connected

Set up seller onboarding for the marketplace: ID document and proof of address, and flag anyone reusing a document. Give me a test link.

create_session_configurationSeller onboarding · 4 steps
create_test_linktest identity “Sam Chen”

Created Seller onboarding in your sandbox: ID document, proof of address and the reuse checks. Test link ready; sending stays off until you switch it on.

Run it on the test identity that reuses a statement.

run_test_sessiontest identity “reused statement”

Needs review: the proof of address was seen in 2 other sessions under different names. Open the session →

Fictional conversation. Verification tools for assistants are coming soon.

What an assistant can do through MCP
  • Prepare and send agreementsTurn a file, template or standard form into a signing request, place and fill fields, report progress. Sending needs a permission you grant.
  • Set up verification workflows Coming soonCompose the steps and checks, take a sandbox key and run test identities.
  • Write and test risk policies Coming soonDraft a policy in plain words, simulate it on test scenarios, and leave publishing to an owner.
  • Read results and route reviews Coming soonFetch a session's evidence and flags and hand a case to a reviewer.

Works with Claude, ChatGPT, Codex and Cursor through one open standard. The assistant never signs for anyone and never decides a case: signing stays with the signer, decisions with your reviewer.

Try it without an account →How assistants work with Korala →
What the reviewer sees

A reused document,
caught before approval.

Anyone can fake a statement now. Korala fingerprints each document and compares it with the sessions before it. When the same statement turns up under another name, your reviewer sees it beside the source before deciding.

SOURCE DOCUMENT Page 1 of 1
NORTHLINE
ENERGY
STATEMENT
ACCOUNT HOLDERSam Chen14 Harbour Lane, Leeds
STATEMENT DATE2 September 2026Account 4471-0928
Electricity · August£64.20
Amount due£64.20
Service address: 14 Harbour Lane, Leeds LS1 4AB

Fictional statement for this example.

Proof of addressReview needed
1Read the document Complete
2Extract and fingerprint Complete
3Compare with earlier sessions Complete
NameSam ChenMatches the ID document
Issue date2 September 2026Within your 3-month window
Document reuseSeen in 2 other sessionsUnder different names

Two other applicants uploaded this same statement. Open those sessions before you decide.

Explore verification

Document evidence
Read identity documents and proofs of address, and record their file, text and field fingerprints.

Risk across sessions
Reused documents, repeat identities, bursts of sign-ups and network clusters. By default, medium and high risk wait for a person.

Sealed results
Every signed PDF carries a long-term PAdES seal and qualified timestamps, so any later change shows.

Document work for your team

Prepare once.
Send for signature.

Reuse templates and standard forms. Organize documents by client or project, then track who has signed.

Reusable documents

Templates and standard forms

  • Service agreementWorkspace template
  • Confidentiality agreementWorkspace template
  • W-9Standard form
Partner onboardingExample
Documents and templates, together

Track your signing requests.

Service agreements · 4 signing requests

  • Alex MorganService agreementCompleted
  • Sam ChenService agreementCompleted
  • Jamie LeeService agreementAwaiting signature
  • Robin EllisService agreementDraft
2 completed1 awaiting signature · 1 draft

  • Reuse templates and forms

    Start recurring requests from templates and standard forms.

  • Organize by client or project

    Group documents and templates by client or project in collections.

  • Track signatures

    Follow signing requests and check which completed files are ready.

Explore document signing
Integrations

Plugs into what
you already use.

Send people a verification link, bring documents in from where they live, keep signing inside your product and send events back to your systems.

Verification links

Send a link. People complete the session on any device and can move from a laptop to their phone with a QR code.

Explore verification →

API and TypeScript client

Sessions, risk assessments, signing and templates behind one key, with tested examples in the developer guide.

Read the API guide →

Embedded signing

Keep the signing experience inside your application with the React components.

Explore signing →

Google Docs & Drive

Choose a document from your Google account, preview it in Korala and prepare it for signing.

Explore Google import →

Webhooks

Document, session, workflow and risk events reach your systems as they happen, signed and with delivery tracking.

Read the webhook guide →
Build with Korala

One API.
Sandbox from minute one.

Take a test key, compose a session from the checks you need and run it in a sandbox kept apart from live data. Your AI assistant reaches the same platform through MCP.

Read the API guideSee the sessions guide →
REST API + TypeScript clientSandbox test keysSessions + workflowsRisk policiesSigned webhooksMCP serverPAdES long-term signatures
Generate documents from Markdown

From source to a reusable template

Write your document in Markdown, fill in names, dates and other details, and add signature fields. Preview the PDF before using the template to create documents.

Explore Markdown templates →
# Service agreement

Between Korala and {{ client.name }}.

## Start date
{{ agreement.start }}

:::signatures
::signature{role="client"}
:::
Help and documentation

Find help
for your task.

Follow a guide to verify customers or sign documents, or find the API instructions for your integration.

Use Korala

Instructions for everyday work.

Review a verification session Prepare and sign a document

Build with Korala

Guides to the API, sessions and risk.

Run a verification session Write a risk policy

Verify your first customer in the sandbox.

Start in the sandboxBuild with the API