For verifiers and platform partners
DigiBridge is a human creation verification platform that gives reviewers a record of the people, process and version behind creative work.
Bring that evidence into film delivery, catalogue intake and platform review. Give registered creators a clear way to show their work, and your team a consistent place to assess it.
Which work and release does this record describe?
Whose contributions and declarations are shared?
What activity is available, and where are the gaps?
What does the current record actually establish?
A record your team can use
What supports the production’s human creation claim?
Ask for the record alongside the delivered cut. Review the selected version, shared contributions and process evidence before accepting a submission or assessing programme eligibility.
A clearer handover from the production team.
Can your intake team get beyond a declaration?
Give submitters a place to provide their DigiBridge record link. Inspect its current status and published evidence alongside your own disclosure, moderation and listing requirements.
A consistent starting point for submission review.
Who stands behind this master?
Connect a delivery to its published creator context, credits and available activity. Keep human creation review distinct from vocal consent, rights ownership and your music delivery checks.
More context for the release entering your catalogue.
Which evidence supports this specific statement?
Locate the shared record, check the version and identify what still needs clarification. Use it alongside contracts, releases and your own assessment of rights and obligations.
A traceable reference for follow up and review.
A stronger submission workflow
A creator should not have to explain their process from scratch every time a new reviewer asks. Keep the shared evidence attached to the version being assessed.
Ask the creator for their published DigiBridge record link or public ID alongside the release. Agree which version and claim your team will assess.
Open the current record. Review the published contribution context, available activity and status. Ask about missing information rather than treating a gap as a finding.
Record your own review outcome under your policies. Keep the DigiBridge reference with the submission so the next reviewer can return to its current public status.
The standard behind the record
DigiBridge combines permitted process evidence, device and creative tool checks, and a dedicated AI verification agent to detect prohibited assistance and software acting in place of a contributor.
Findings must stay connected to evidence and the contributor’s explanation. Ordinary playback, sequencing, keyframes and rendering are assessed under the tool’s disclosed policy.
Read the programme rulesThe affected recording or version is held from programme publication. The contributor can review the evidence and challenge the finding.
The project becomes ineligible for directory publication. An AI suspicion or recording gap alone is not an incident.
Source footage, project files and typed content stay outside evidence collection. Reviewers see the information approved for sharing, not private workspace activity.
API and organisation access
Paid verifier and API engagements are scoped around your review process, integration needs and support requirements. Start with the decision your team makes and the evidence it needs.
The public v1 API resolves approved public records by ID or slug. It returns shared fields and explicit status. It does not run an AI assessment or return private evidence, and its response must not be presented as a final human creation certificate.
Connect the submission reference to the current public record.
GET /api/verifier/v1/resolve?code=<publicVerifyId_or_slug>A PLACE IN THE CREDITS
The people made the work.
The record tells their story.
Proposed credits placement
The credits strategy
Our aim is for an eligible film or programme to carry its DigiBridge reference in opening or closing credits, with the same link in delivery notes and online descriptions. Viewers and reviewers can follow it back to the specific release.
Programme badges belong only on versions authorised under the publication rules. A record ID is a reference, not approval by itself. A changed cut, held version or withdrawn record must never borrow the status of a different release.
Understand a published recordThe wider publishing landscape
DigiBridge adds a record of the creative process to your review. Your platform’s disclosure rules, rights checks and editorial decisions still apply.
Requires disclosure for meaningful AI changes to realistic content and may apply labels using its own detection and other signals.
Read the platform policyUse AI info labels informed by technical signals and disclosure, with context about how content was made or edited.
Read the platform policyAddresses vocal impersonation and AI credits. Its guidance explicitly says that no AI credit does not mean AI was not used.
Read the platform policyPolicy examples checked on 30 September 2026. These companies are named for context, with no partnership or endorsement implied. A DigiBridge record does not settle copyright ownership, contractual rights or a platform’s acceptance decision.
Build a clearer review process
Bring your submission workflow, the decisions you make and the evidence your team needs. We can discuss the right review and integration scope.