Models¶

Moveris currently serves the Mixed V3.1.1 family. Three aliases ship in production: 30, 60, and 120 frames.

In plain terms

Pick how many camera frames to send. Thirty frames is the default — about one second of capture. Use 60 or 120 when you need more temporal signal.

	30f Default	60f	120f
Model ID	`mixed-30-v3_1_1`	`mixed-60-v3_1_1`	`mixed-120-v3_1_1`
Frames	30	60	120
Capture time	~1 s	~2 s	~4 s
Best for	Default KYC and in-app checks	Higher-security onboarding	Maximum temporal coverage

Model cards

Detailed model cards with full metrics and evaluation data are available in the Developer Portal. Sign in to access them.

Not sure? Start with mixed-30-v3_1_1

This is the API default, the SDK default (DEFAULT_MODEL), and the Meet default. Pin the alias explicitly. Do not omit model and do not send a retired id.

When to Use Each¶

30 frames (mixed-30-v3_1_1) — Standard identity verification, account creation, in-app SDK capture.

60 frames (mixed-60-v3_1_1) — Higher-security onboarding when users will tolerate a longer check.

120 frames (mixed-120-v3_1_1) — Highest scrutiny: high-value flows or when you need maximum temporal coverage.

How Frames Affect Results¶

More frames give the temporal-physio model more signal across time. Send exactly the frame count in the alias. mixed-30-v3_1_1 expects 30 consecutive frames, mixed-60-v3_1_1 expects 60, mixed-120-v3_1_1 expects 120.

{
  "session_id": "...",
  "model": "mixed-30-v3_1_1",
  "frames": [...]
}

The SDK exports DEFAULT_MODEL (mixed-30-v3_1_1) and VALID_FRAME_COUNTS ([30, 60, 120]). Call getModels() or useModels() for the live registry.

Retired aliases

These ids are no longer served. Requests that pin them fail.

Mixed V2 (mixed-*-v2) and the numeric aliases (50, 250)
Mixed V3 / V3.1 aliases (mixed-*-v3, mixed-*-v3_1) — pin V3.1.1 instead

See Model Versioning & Frames for X-Model-Version and frame counts.