KYC/KYB Hooks

info

Active portfolio classification — 2026-07-25 [D]. KYC/KYB Hooks is a pre-launch onboarding-integration capability inside Skyzai Work, not an independent SKU, package, identity verifier, or authority source. Product, pricing, commercial-page, and standalone-launch language below is preserved design history; linked routes are compatibility coordinates, not deployment or regulated-provider proof.

note

Current public-DAV authority boundary — 2026-07-12. Pre-launch target design; nothing here proves a live system. A public-DAV consequence may occur only when at least two natural-person councilors bind the exact consequence in a complete valid bound PRISM decision receipt. PRISM records and verifies that receipt only; it never serves as council, signatory, authority, or receipt producer. AI and caste seats stage unsigned proposals only; they never authorize or execute a public-DAV consequence. Constitution or membership adoption establishes constitution and membership only; it does not authorize a later consequence. Policy may constrain an unsigned proposal but never authorizes execution or substitutes for the complete consequence-bound receipt. Before receipt validity, consequence fails closed to read-only proposal, simulation, or deterministic sandbox; live evidence remains gated_pending_complete_valid_bound_receipt. Software deterministically carries out only the exact consequence bound to a complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact consequence.

Scope: capability inside the two buyer products (Skyzai Personal / Skyzai Work ✱) — not a standalone SKU. See The Product Family.

Surface: kyc.skyzai.com (declarative) Catalog route: skyzai.com/products/kyc-kyb-hooks/ Status: SPEC Evidence tier: [D] — schema + hook events specified; first external integration is the proof gate (re-tiered [B]→[D] 2026-07-03 per TIER_MERGE_GATE: a spec/draft is not an observed run; [B] requires a dated reproducible receipt) Source canon: 02_SKYZAI/02_ORGANISM_COMMONS/NOOSPHERE/03_PRODUCTS/kyc_kyb_hooks/WEBSITE.md

What KYC/KYB Hooks Are

KYC/KYB Hooks are an integration layer — not a regulated identity provider. They:

Capture structured onboarding evidence from entities and individuals
Route checks to verified third-party KYC/KYB providers
Emit structured evidence packets with provider receipts
Export compliance-ready audit trails

Critical boundary: Skyzai does not claim to be a regulated KYC/KYB provider unless counsel explicitly ratifies that path. This service is plumbing, not the pipe.

Architecture

┌─────────────┐     ┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│  Onboarding │────▶│  Evidence   │────▶│  Provider   │────▶│  Provider   │
│  Intake     │     │  Capture    │     │  Router     │     │  (3rd party)│
└─────────────┘     └─────────────┘     └─────────────┘     └─────────────┘
       │                     │                     │                     │
       │                     ▼                     ▼                     ▼
       │              ┌─────────────┐     ┌─────────────┐     ┌─────────────┐
       │              │  EvoNet     │     │  Provider   │     │  Provider   │
       │              │  SHOULD NOT │     │  Receipt    │     │  Response   │
       │              └─────────────┘     └─────────────┘     └─────────────┘
       │                     │                     │                     │
       │                     ▼                     ▼                     ▼
       │              ┌─────────────┐     ┌─────────────┐     ┌─────────────┐
       └─────────────▶│ Sovereign   │     │  Evidence   │     │  OFN        │
                      │ Gate (PRISM)│     │  Packet     │     │  Receipt    │
                      └─────────────┘     └─────────────┘     └─────────────┘

The Sovereign Gate routes public-DAV high-risk checks through a complete valid bound PRISM decision receipt from at least two natural-person councilors binding the exact consequence. PRISM records and verifies only; AI/caste seats remain unsigned. Any Legal Person check still requires lawful external authority and the executors required by jurisdiction, with counsel conditional.

The exact superseded transition line follows as dated K3 provenance.

The Sovereign Gate routes high-risk checks through PRISM council ratification (post-2026-05-09 public-DAV transition); historical envelopes pre-transition are K2-signed.

Evidence Capture Schema

Individual (KYC)

{
  "check_type": "kyc_individual",
  "subject": {
    "full_name": "...",
    "date_of_birth": "...",
    "nationality": "...",
    "residential_address": "..."
  },
  "documents": {
    "id_document": {"type": "passport", "hash": "..."},
    "proof_of_address": {"type": "utility_bill", "hash": "..."}
  },
  "self_attestation": {
    "timestamp": "...",
    "declaration": "I confirm the above is true..."
  }
}

Entity (KYB)

{
  "check_type": "kyb_entity",
  "entity": {
    "legal_name": "...",
    "incorporation_jurisdiction": "...",
    "registration_number": "...",
    "business_address": "..."
  },
  "ubo": [
    {"name": "...", "ownership_percentage": "25%", "verification_status": "..."}
  ],
  "directors": [...],
  "documents": {
    "certificate_of_incorporation": {"hash": "..."},
    "articles_of_association": {"hash": "..."}
  }
}

Provider Routing

Supported Providers

Provider	Capabilities	Regions	Status
Onfido	Document verify, biometric	Global	Planned
Jumio	KYC, KYB, AML	Global	Planned
Trulioo	Global identity verify	195+ countries	Planned
Shufti Pro	KYC, KYB, video KYC	Global	Planned

Routing Logic

def route_check(evidence: dict) -> Provider:
    # Jurisdiction-based routing
    if evidence["jurisdiction"] in EU:
        return Provider.GDPR_COMPLIANT

    # Risk-based routing
    if evidence["risk_score"] > 0.7:
        return Provider.ENHANCED_DUE_DILIGENCE

    # Default routing
    return Provider.STANDARD

API Specification

`POST /v1/kyc/checks`

Submit individual KYC check.

Request:

{
  "check_type": "kyc_individual",
  "subject": {...},
  "documents": {...},
  "provider_preference": "onfido"
}

Response:

{
  "check_id": "kyc_2026_abc123",
  "status": "pending",
  "provider": "onfido",
  "estimated_completion": "2026-05-09T14:00:00Z",
  "webhook_url": "https://..."
}

`POST /v1/kyb/checks`

Submit entity KYB check.

`GET /v1/checks/{id}`

Retrieve check status and results.

`GET /v1/checks/{id}/export`

Export compliance-ready evidence packet.

Evidence Tiers

Tier	Claim	Required Evidence
[I]	KYC/KYB Hooks architecture is defined	Design document, API spec
[B]	Provider routing works in test	Integration tests with sandbox providers
[E]	External customer uses KYC/KYB Hooks	Customer integration proof, provider receipts
[A]	KYC/KYB Hooks used in regulated context	Counsel opinion, regulatory correspondence

Current status: [B] — schema + hook events specified; reference adapter scaffolds exist; first external integration is the proof gate.

What This Service Is NOT

Not a regulated KYC/KYB provider
Not a financial institution
Not a legal identity verifier
Not an AML/CFT compliance officer
Not a screening guarantee or compliance attestation
No legal-compliance guarantee for the buyer's jurisdiction

What This Service IS

An integration layer between your onboarding flow and verified providers
An evidence capture and routing system
An audit trail generator
A pass-through cost handler (provider fees pass through without markup)

η = 0 Compliance

Chargeable	Not Chargeable
Integration setup	Provider check fees (pass-through)
Evidence routing	Identity verification itself
Controls and monitoring	Regulatory attestation
Support	Compliance guarantee

Cross-links

Product page: /products/kyc-kyb-hooks/
Buyer deck: /products/kyc-kyb-hooks/deck/
Resource room: /products/kyc-kyb-hooks/resources/
Access form: /products/kyc-kyb-hooks/access/
Adjacent canon: API Pay (P0), API contracts (35), Wallet Boundaries (P3)
Source markdown: 02_SKYZAI/02_ORGANISM_COMMONS/NOOSPHERE/03_PRODUCTS/kyc_kyb_hooks/WEBSITE.md
Validator code: 02_SKYZAI/02_ORGANISM_COMMONS/EXECUTION/SKYZAI/CORE/a7_validator.py

Zero-Sum Resolution Equation

K3 public-DAV authority history — 2026-07-12

K3 historical reference — not active authority

note

Current public-DAV boundary — 2026-07-10. Pre-launch target design; nothing here is live. The active DAV is public and targets PRISM, with no K2 runtime, launch, genesis/bootstrap, or fallback dependency. Consequential authority requires at least two natural-person councilors; AI/caste seats stage unsigned proposals only. Before quorum, behavior fails closed to read-only/proposal, simulation, or deterministic sandbox, and a live decision receipt remains gated pending quorum.

The Sovereign Gate routes public-DAV high-risk checks through a decision receipt signed by at least two natural-person PRISM councilors. AI/caste seats remain unsigned.

What KYC/KYB Hooks Are​

Architecture​

Evidence Capture Schema​

Individual (KYC)​

Entity (KYB)​

Provider Routing​

Supported Providers​

Routing Logic​

API Specification​

POST /v1/kyc/checks​

POST /v1/kyb/checks​

GET /v1/checks/{id}​

GET /v1/checks/{id}/export​

Evidence Tiers​

What This Service Is NOT​

What This Service IS​

η = 0 Compliance​

Cross-links​

K3 public-DAV authority history — 2026-07-12​