Documentation
Learn how to use OCME Registry for content creation and verification
Reference
Entity Types
OCME Registry assigns a Decentralized Identifier (DID) to every registered entity. Each DID
carries an entity-type segment: did:webvh:{domain}:{entityType}:{id}.
Registered Entities
creator
A person or group that owns registered works. Creator DIDs anchor identity, attribution, and
(on authenticated views) payment and compliance material. Resolves publicly at /creator/{id}/did.json.
content
A registered work — a video, audio track, or image — with its metadata, fingerprint (SHA-256 file hash), and ownership chain.
media
The underlying media asset of a content record (the stored file and its technical metadata, such as duration and storage location).
splitsheet
A revenue-split agreement attached to content, recording collaborators and their share percentages. Collaborators claim splitsheet invites through the OCMECO app.
showrunner
A production/broadcast identity that organizes content into programs and sites. Resolves
publicly at /showrunner/{slug}/did.json.
member
A platform member identity, referenced by a hash rather than a raw id. Resolves publicly at /member/{hash}/did.json.
cube
A CubiCube entity — the companion app surface for members — registered with its own DID and readable through the authenticated service-binding API.
Verifying an Entity
Any of these DIDs can be verified through POST /api/verify/did or the verification tools. Creator documents served publicly are privacy-redacted — see the DID Method Guide.