Identity checks built for financial products
Check a person, a company, or an AI agent once. After that they can prove a single fact — old enough, real company, allowed to trade — without handing over the documents behind it.
Prove one fact
ZK
without showing the data
Checked
Accredited investor
Valid · the documents stayed private
Private by default
Only the fact you asked for is shared.
Status
Checked and trusted
Risk score · 12 / 100
A person, a company, and an AI agent each need a different check. You run all three the same way, and each one is looked at as closely as the risk deserves.
You picked
KYC · Checking a person
Once someone has been checked, the result can be reused as a simple yes. Their documents stay where they are.
answer = { over_18: true, risk: "low", documents: "private" }Most checks end with a copy of someone's passport sitting in a database. This one ends with a yes or no that anyone can verify — and nothing else changes hands.
Check once
The documents come to us, and they stay with us.
Make a proof
It answers one question, and carries nothing else.
Share the answer
Whoever asked gets a yes they can check for themselves.
What gets shared
Private session
Stays with us
Leaves as a proof
Accredited investor
Valid for 24 hours
Signed, and anyone can check it
DOCUMENTS IN → CHECK → ONE ANSWER OUT
No personal data crosses this line.
The steps a compliance team already does by hand — background checks, sanctions lists, watching for odd activity, scoring, investigating, escalating, reporting — in one place, with a record kept at every step.
People and companies
Watchlist matches
Unusual activity, as it happens
Updated as things change
Cases, evidence, handovers
Ready for the regulator
From the first signal to a written outcome
Every step recorded
Built to support anti-money-laundering rules and the reporting your regulator expects
Nobody should have to send the same passport photo to five different teams. A finished check travels with the person, the company, or the agent it belongs to.
One check covers their account, their payments, and what they can open.
The company, its owners, and who is allowed to sign — settled once.
What the software is, what it may do, and the limits it works within.
Take the result into any product that needs to know.
const check = await identity.verify({
who: "business",
rules: "kyb.standard",
prove: ["real_company", "signer_allowed"],
privacy: "zero_knowledge"
});
// what comes back
{ status: "verified", proof: "zkp_••••", risk: "low" }3
kinds of customer: people, companies, AI agents
1
check, reused everywhere it is needed
0
documents handed over to prove a single fact
Check who you are dealing with without turning your own product into a filing cabinet of other people's documents.
Start buildingOne kind of account works for a person, a company, or an agent. Who was checked, what they may do, and what they can spend all sit on the same record.
Nothing gets permission to move money until we know who is asking and what they are allowed to do.
A payment can confirm someone qualifies without opening their whole record to do it.
Every extra copy of someone's ID is a copy you have to protect. The less you hold, the less there is to lose.
Collect what the decision actually needs, and nothing beyond it.
Prove a single thing instead of handing over everything at once.
One finished check can serve every product that needs the same answer.
Software can prove it is allowed to act without exposing who it works for.
Show your work to a regulator without moving personal data around to do it.
Spending limits and approvals live on the account, not in someone's process notes.
People, companies, and agents get a way to prove themselves. You get far less personal data to look after.