Beta-1 KYC + identity network

Aegir now runs a real Beta-1 KYC decision path instead of a pass/review-only placeholder.

This flow collects consent, document and selfie evidence, device and browser fingerprints, and a browser-side camera authenticity assessment. The submission is normalized through the Beta-1 Node-shaped KYC contract, enriched with Foxlin.Research, scored for trust and risk, and returned with an identity-network token when the verification passes.

Beta-1 capture path

What this page is doing now

  • Document capture, selfie capture, device fingerprinting, and consent flags are collected in the web flow.
  • Camera authenticity analysis uses browser-available heuristics only in Beta-1 and should later shift more aggressively into the Aegir app.
  • Vendor scoring is normalized through the Beta-1 Node-shaped microservice contract before trust and risk are computed.
  • Foxlin.Research remains advisory and can trigger review signals, but it does not directly issue identity trust.
Current limits

What is still intentionally Beta-1 scoped

  • Vendor APIs are represented through the Beta-1 normalized microservice contract, not live production credentials on this page.
  • Camera authenticity uses browser-available heuristics and should later lean more heavily on the desktop/mobile Aegir app.
  • Foxlin.Research remains advisory and still does not directly issue or revoke trust by itself.
Capture form

Run the Beta-1 KYC pipeline

Runtime capture

Device, browser, and camera heuristics

Run the browser-side analysis before submitting so the Beta-1 pipeline has fingerprint and camera authenticity inputs.

Not analyzed
Awaiting runtime capture analysis...
Return to User Dashboard