TitleGraph Documentation

TitleGraph is an open standard designed to solve the hardest data interoperability problems in modern streaming television. By leveraging the AT Protocol, it allows content owners to cryptographically sign and syndicate catalogs, live linear broadcast events, and commercial availability rules to a decentralized network.

2. Core Architecture

Legacy entertainment metadata traditionally binds the creative work directly to its commercial distribution, creating fragmented, proprietary silos. TitleGraph introduces a strict architectural decoupling: we separate the art from the commerce.

The Catalog Namespace

Mapped strictly to W3C schema.org/CreativeWork semantics, this namespace defines the canonical record of the media. It defines what the art is, completely independent of how it is sold. A Movie record contains its EIDR, runtime, and portrait key art, but holds zero information regarding its geographic availability.

The Delivery Namespace

Mapped to schema.org/Offer, this namespace dictates the commercial topology. It handles complex geo-fencing (spotbeams and blackouts), VOD pricing logic, and entitlement bundles. An Offer record acts as a commercial wrapper pointing to a specific Catalog asset.

3. Built on the AT Protocol

TitleGraph is not a centralized API. It is a collection of Lexicons built for the Authenticated Transfer (AT) Protocol.

  • Personal Data Servers (PDS): Streaming networks (like Moonstone Hubs) host their own PDS, granting them absolute sovereign control over their metadata firehose.
  • Cryptographic Verification: Because records are tied to decentralized identifiers (DIDs), aggregators can mathematically verify that a metadata update actually originated from the content owner.
  • Global Firehose: MVPDs and aggregators do not need to build dozens of bespoke API integrations. They simply subscribe to the TitleGraph Relay and filter for the org.titlegraph namespace.

4. Resolving Entitlements

To render a catalog on a consumer television UI, an aggregator must resolve the relationship between the Offer and the Asset. The resolution chain flows backward:

  1. The Client reads the org.titlegraph.delivery.offer record.
  2. It verifies the offerGeoEligibility against the user's IP address.
  3. If valid, it follows the entitlementRef to find the logical rights grouping.
  4. It follows the targetRefs within the entitlement to fetch the underlying org.titlegraph.catalog.movie records to render the posters and titles.