印 INKAN
Book demo
No.01Product · Standard

The rail beneath
biometric AI.

Capture, License, Remit. One API surface, four jurisdictions, a receipt that holds up in court. We do not moderate models. We do not rank creators. We sign the consent, log the use, and pay the talent.

No.02How it works

One ceremony. One signature. Every use after.

The same four steps every time, regardless of model, brand, or jurisdiction. Mono-numerals connect the steps; hair-rules connect the ledger.

  1. 01

    Capture the ceremony.

    Talent signs once, in-person or remote, against a witnessed liveness check. The biometric template is hashed to a one-way commitment; the raw frames never leave the device. Jurisdiction is bound to the record at this step — UK, EU, US state-level, or all four.

    CEREMONY · LIVENESS · HASH

  2. 02

    Sign the receipt.

    INKAN issues a detached Ed25519 signature over the consent payload. The receipt is human-readable, machine-verifiable, and carries an embedded revocation handle. We append it to the public ledger and return the record ID.

    ED25519 · LEDGER · ID

  3. 03

    License the likeness.

    Brands and agencies fetch the licensed likeness through our SDKs or directly via the API. The receipt travels with the file across every render, every plug-in, every downstream system — Adobe, Runway, your DAM, your render farm.

    API · ADOBE · RUNWAY · DAM

  4. 04

    Remit on every event.

    Each generation event lands on the royalty ledger. Talent is paid per use through Stripe Connect or a withdrawal API. Brands receive an audit trail that holds across four jurisdictions and one regulator. Withdrawal of consent is honoured within 24 hours.

    LEDGER · STRIPE · WITHDRAW

No.03API surface

Everything is a signed receipt.

One request to capture consent. One response with a record ID, Ed25519 signature, and a verifiable Merkle leaf on the public ledger. No webhooks required to read the result.

Request
POST /v1/consent HTTP/1.1
Host: api.inkanbio.com
Authorization: Bearer sk_live_3K9v2x...
Content-Type: application/json
Idempotency-Key: 5d0a8e21-7c4a-4f12-9d21-8f7f0a5d11c1

{
  "subject": {
    "id": "tlt_8f3a72b",
    "display": "Lucia Vance"
  },
  "biometric": {
    "template_hash": "sha256:8c1e4...e2",
    "liveness_score": 0.987,
    "captured_at": "2026-04-12T14:33:08Z"
  },
  "jurisdiction": ["UK", "EU", "ES"],
  "scope": {
    "category": ["editorial", "brand"],
    "term_months": 24,
    "exclusivity": "non-exclusive"
  },
  "royalty": {
    "currency": "GBP",
    "per_event_minor": 4000,
    "remit_to": "stripe_acct_1NkAn..."
  },
  "expires_at": "2028-04-12T14:33:08Z"
}
Response
HTTP/1.1 201 Created
Content-Type: application/json

{
  "id": "rec_INK-0X4F.A12C.7B19",
  "status": "active",
  "created_at": "2026-04-12T14:33:09Z",
  "signature": {
    "alg": "Ed25519",
    "kid": "ink-prod-2026-04",
    "value": "MEUCIQDk1...jwIgZ8w"
  },
  "ledger": {
    "epoch": 142,
    "leaf_index": 18074,
    "merkle_root": "ed3a...c4f1"
  },
  "revoke_url": "https://api.inkanbio.com/v1/consent/rec_INK-0X4F.../revoke",
  "verify_url": "https://verify.inkanbio.com/rec_INK-0X4F..."
}
  • A
    Idempotency by default. Resubmit the same Idempotency-Key and you'll get the same record back — never two consents for one ceremony.
  • B
    Detached Ed25519 signature. Every receipt verifies offline against our published JWK set. No live API call required to prove the consent existed.
  • C
    Merkle-anchored ledger. Each record is a leaf in an epoch-rooted tree. Brands can prove inclusion to a regulator without revealing other records.
  • D
    24-hour revocation SLA. Talent revokes through a self-serve URL embedded in the receipt. Downstream renders are blocked at the next license check.
Next

Talk to the team that's signing the standard.

Twenty minutes on a call. Live receipt walkthrough, Q&A on jurisdiction coverage, and a printed copy of the spec.

Book a 20-min call Read the developer docs