Skip to content

For Decision-Makers

A high-level overview for product managers, QA leads, and stakeholders. Understand what Moveris does, why it matters, and how it fits into your product.

What Moveris Does (Plain Terms)

Moveris answers one question: Is there a real, living person in front of the camera right now?

Unlike passwords or 2FA, which can be stolen or bypassed, Moveris uses biological signals that are hard to fake—subtle movements, micro-expressions, and physiological reactions that occur involuntarily. Deepfakes and AI-generated faces can look convincing, but they cannot replicate these live biological patterns.

In practice

Your app captures video from the user's camera, sends frames (e.g. 10 for the fast model, 30 for the balanced model) to Moveris, and receives a verdict: live (real person) or fake (spoofing attempt), with a confidence score.

When to Use Liveness Detection

Use Case Why Moveris Helps
Account opening / KYC Prove the applicant is physically present—not a stolen identity or deepfake
High-value transactions Step-up authentication before wire transfers, contract signing, or admin actions
Account recovery Verify the person requesting access is the real account owner
Bot prevention Replace CAPTCHAs with frictionless liveness checks
AI agent authorization When AI agents perform actions on behalf of users, verify a human authorized it (see MCP Integration)

Integration Paths (Non-Technical)

Path Best For Effort Time to Integrate
SDK (React / React Native) Web and mobile apps Low 5–30 minutes
Direct API Custom stacks, backend-only flows Medium 1–2 hours
AI Agents (MCP) Cowork, Claude, and MCP-compatible hosts Low (if already using MCP) Configure MCP server

Developer Portal

API keys, usage tracking, billing, and analytics are managed in the Moveris Developer Portal:

Open Developer Portal

The portal lets you:

  • Create and manage API keys
  • View usage and credits
  • Access interactive API docs
  • Monitor billing

AI Agents and MCP

Moveris offers an MCP (Model Context Protocol) server for AI agents. When an AI agent is about to perform a high-stakes action—e.g., signing a contract or initiating a transfer—it can call Moveris to verify that a live human authorized that action.

This is step-up authentication for the agent era: the agent surfaces a verification link to the user, the user completes a short liveness check in the browser, and the agent receives a signed attestation before proceeding.

For technical details

See the API Reference and SDK Overview for implementation details. The MCP server documentation is available separately for AI agent integrations.

Key Metrics at a Glance

Metric Typical Value
Verification time < 1 second (model-dependent: 10–30 frames typical)
Frames required 10
Confidence score 0–100 (65+ = live)
Processing time ~245 ms server-side

Next Steps