Start here
Choose the outcome you need.
Creators and contributors
Connect your own account, choose the right project and understand what recording covers. Keep your footage, audio and project files private.
Producers and studio teams
Invite people with the right access, keep credits separate from permissions and prepare a selected cut or deliverable for review.
Reviewers and commissioning teams
Check the delivered version, contributor declarations, recording coverage and current status before making your decision.
Platforms and developers
Resolve a public record, preserve its status and connect the permitted response to your submission or review interface.
Security and compliance teams
Review collection boundaries, consent, access controls and the information exposed by each interface.
Understand verification
See how device checks, creative tool observations and the AI verification agent support the human creation standard.
Platform model
The record from creation to review.
A record for the recipient
Share selected information about the work and its current status. The public API returns only approved fields; private records remain unavailable.
A workspace for the production
Organise projects, assets and contributors. An asset is a specific work or deliverable, such as an edit, a news package or a music master.
A record of permitted activity
The Mac workflow connects supported creative tools to the selected project. Signing in, choosing a file and starting recording are separate steps.
Start here
Query an approved public record.
/api/verifier/v1Discover the current API
Returns the API version, current status, endpoint paths and release notices.
Access: Public, no API key
/api/verifier/v1/resolve?code=<publicVerifyId_or_slug>Resolve a public record
Looks up an active approved preview by its public verify ID or public slug.
Access: Public, no API key
curl https://digibridge-home-pages.vercel.app/api/verifier/v1/health
curl "https://digibridge-home-pages.vercel.app/api/verifier/v1/resolve?code=<publicVerifyId_or_slug>"Privacy contract
Give recipients the information approved for sharing.
Never returned by the Verifier API
The public resolver is built around a public safe data projection. Pending, rejected, unpublished, private, redacted, embargoed and ZK only records do not reveal whether a private record exists.
- Workspace, owner, internal asset or project IDs
- Raw proof events, evidence or manifest JSON
- Contributor emails or private identity data
- Device credentials, keys or local paths
- Source media, stems, masters or project files
- Verification conclusions beyond the response status
Documentation paths
Go directly to the surface you need.
Production workflow
Prepare a project, invite contributors and understand recording and delivery.
Review a record
Check the version, coverage, declarations and status of a submitted work.
Roles and sharing
Choose account access, confirm contributions and prepare a public selection.
Verification engine
Understand the checks, AI analysis, warnings and programme rules.
Quick start
Make a real request and interpret the current response shape.
API reference
Review every current Verifier API route, response and not found boundary.
Authentication
Understand public, workspace and paired device access models.
HTTP clients and SDKs
Use ordinary HTTPS requests and find guidance on official client packages.
Device interfaces
Review the development contract for paired devices and signed event submission.
Security model
Inspect public data minimisation, device validation and current limitations.
Evidence model
Keep identity, observed activity, declarations and authorship distinct.
Record integrity
Understand signed sources, corrections and publication history.
Support
Interpret errors and send a report without private project material.