verification infrastructure

Verification that remembers the last time.

Most verification systems treat every login as if it were the first. Omega links each verification to the one before it — so you know whether this is a continuation, or something new.

each verification carries forward from the last
Get your API key Read the docs

Three steps. Two API calls.

Omega handles code generation, delivery, expiry, and single-use enforcement — and hands back a continuity signal you didn't have before.

01

Request

Your app asks Omega to verify a user. A single-use code goes out by email, valid for ten minutes.

02

Verify

The user enters the code. Omega confirms it, burns it, and returns a token for next time.

03

Continue

Present that token on the next verification and Omega tells you whether this session genuinely follows the last one.

A signal you can act on.

Every verification returns a continuity status. What you do with it is up to you — allow, challenge, or flag.

first No prior history. A clean start.
ok Confirmed continuation of the last verification.
broken Continuity couldn't be confirmed. Worth a second look.
  • Never blocks your usersA broken chain is information, not a wall. Verification always completes through the normal path.
  • Single-use, ten-minute codesExpiry and replay protection are enforced by the engine, not left to your integration.
  • Two endpoints, plain HTTPNo SDK to install, no framework to adopt. Works with whatever you already run.
  • Optional by designUse the continuity feature or ignore it. Omega works as a straightforward verification service either way.
Get started

Two calls away.

Email or call us to request a key. You can be verifying users this afternoon.

Email support Call 1-866-588-8182 Read the docs