Skip to main content
KYC belongs to an identity. A verification is a case in which each member (an owner, a responsible party) completes a hosted identity check. Forming a company is a separate step, and it starts only once the case is ready — see Legal. The flow is short:
  1. Start a case with POST /v1/identities/{id}/legal/verifications, naming the members.
  2. Give the primary member the returned link; every other member is emailed theirs. The primary is never emailed — their link is on the create response and on every resend, and null on reads.
  3. Read GET /v1/identities/{id}/legal/verifications/{vid} until ready_for_formation is true.
Naive Managed Agents stores a member’s name and email only. Date of birth, tax ids and home addresses are collected on the hosted page and never cross Managed Agents’ API, rows or audit log. A hosted link is returned once, on the response that minted it, and is null on every later read; resend mints a new one.

​
Lifecycle

A member is pending → link_ready (or link_sent once emailed) → in_progress → pending_review | verified | failed. verified and failed are final: a redelivered callback or a later read never changes them. The case is failed if any member failed, else pending_review if any member is under review, else verified once every member is, else in_progress. ready_for_formation is true only when the case is verified.

​
From an agent

A session whose identity can be verified is offered legal.verifications, legal.verification, legal.verify and legal.resend_link. Starting a case and resending a link ask a person by default. The wire for every field is Legal.
CLI

Next: form a company

A verified case is what a company formation requires.