How Helios works

Helios is SAGEA's identity verification infrastructure. It verifies a real person holding a real document, then returns a structured KYC decision you can trust in production.

Capture a liveness video (short selfie video) + front and back ID images
Helios checks document authenticity, face match, and liveness with anti-spoofing
You get a synchronous decision: approved, review, or declined, with scores and reasons

Hosted endpoints:

POST https://api.sagea.space/helios/kyc/v1
POST https://api.sagea.space/helios/kyc/v2

Both require an API key in the Authorization header. See the KYC cookbook to run your first verification.

The pipeline

1. Capture

Your client collects three artifacts:

Artifact	Requirements
`front_image`	JPG/PNG, ID front fully visible, min 1200px wide
`back_image`	JPG/PNG, ID back fully visible (v1 requires both sides)
`liveness_video`	MP4/MOV/WebM, 3–10s selfie video, single face, good light

2. Verify

Helios runs three checks in parallel:

Document authenticity: security features, fonts, layout, MRZ/barcode consistency.
Face match: selfie frames vs portrait cropped from front_image.
Liveness + anti-spoofing: motion, texture, and depth cues from the video. Photos of screens and printed faces are rejected.

3. Decide

Each check returns a 0–1 score plus an overall decision:

Decision	Meaning
`approved`	All checks pass above threshold
`review`	Borderline — send to manual review
`declined`	Failed authenticity, face match, or liveness

The response also includes extracted fields (name, document number, date of birth, expiry) when the document is readable.

v1 vs v2

	v1	v2
Path	`POST https://api.sagea.space/helios/kyc/v1`	`POST https://api.sagea.space/helios/kyc/v2`
Format	`multipart/form-data` with files	JSON with base64 or multipart
Images	`front_image` + `back_image` required	`front_image` required, `back_image` optional (single-sided docs)
Video	`liveness_video` required	`liveness_video` required, plus optional `document_video`
Best for	Web/mobile uploads	Server-side integrations and back-office pipelines

Both endpoints use the same auth and return the same decision schema.

Security notes

Send files over HTTPS only. Never log raw videos or ID images.
Keys are per-workspace. Rotate on employee offboarding or suspected leak.
Retain verification IDs, not media, unless your retention policy requires otherwise.