Skip to Content
CerebrumDocs
GuidesAPI referenceTrust & security

Cerebrum documentation

Integrate identity verification, manage your workflow, and understand your results.

What would you like to do?

Build an integration, send a verification invite, or review an order. Start with the path that matches your work.

New to the platform? Set up your account. Connecting Tazworks? Onboard a client.


Find the documentation you need

Tutorials

Learn by doing. Follow a guided example from your first request to a verification result.

Complete your first API verification →

Before you begin, have an API key and a package ID ready. The authentication guide explains how to get and test your key.


Keep your workflow moving

Track an invite · Create a reorder · Manage package access · Review failure scenarios

Need a hand with access, configuration, or an integration? Contact Cerebrum support.

Platform vocabulary

  • Cerebrum is the platform; Cortex API is its integration API.
  • Cognition is the dashboard for invitations and applicant workflows. Cortex is the dashboard for order review and administration.
  • vID is the applicant's identity-verification experience, available through supported web and app invite flows.
  • A package, called a package set in parts of the API, configures the requested checks. Retain the identifier returned by the package API; see Packages.
  • An invite starts an applicant journey. An order tracks verification or screening work and its results. Store each resource's own identifier.
  • A Beam processes structured inputs into credentials. These advanced resources have their own lifecycle; see Working with Beams.

API releases and documentation changes

The downloadable OpenAPI document records the backend software release in info.version. The /v1 prefix belongs to the API route, so it is a different identifier from the release number. Content status records the reviewed snapshot's source, retrieval time, version, and hash.

November 19, 2026 documentation review

This review corrects contract annotations, integration workflows, and generated reference/search/Markdown behavior. Source-verified documentation corrections are applied consistently to the website and downloadable specification. They do not change API runtime behavior.

For deprecation and migration decisions, check an operation's deprecation marker and its replacement guidance. Ask Cerebrum about the affected environment before planning a cutover; a documentation release does not imply a new API compatibility version or a retirement date.

On this page