Publish a CUME fan channel.
Publish a continuous station on your own domain. The marker below opts it into CUME discovery and review. Official listing is a separate editorial decision.
1. Make the station readable
Serve a public homepage, a continuous playback manifest, and a catalog of complete epochs. Use ordinary links, headings, meaningful titles and timed captions where available. Keep operator credentials private.
2. Publish the manifest
Serve /.well-known/cume-channel.json as application/json over HTTPS, without authentication. Use stable station and channel identifiers. Fan stations declare relationship: "fan".
{
"protocol": "cume-channel",
"version": 1,
"optIn": true,
"network": "CUME",
"station": {
"id": "https://tv.example.org",
"name": "Your station",
"url": "https://tv.example.org",
"description": "The idea behind your channel.",
"language": "en",
"relationship": "fan"
},
"channels": [
{
"id": "shapes-after-dark",
"name": "Shapes After Dark",
"watchUrl": "https://tv.example.org/watch",
"manifestUrl": "https://tv.example.org/api/manifest",
"epochsUrl": "https://tv.example.org/api/epochs"
}
]
}3. Add the discovery tag
Place this in the homepage's HTML head:
<link rel="cume-channel" type="application/json" href="/.well-known/cume-channel.json">
The discovery key is protocol: "cume-channel", with version: 1, network: "CUME" and optIn: true. Removing the tag or setting optIn: false withdraws the opt-in. Consumers must recheck it before listing a station.
Playback and epoch shapes
A playback response has a channel with id, label and title; ordered clips; latestSequence; playbackStartSequence; and updatedAt. Each clip has a stable id, increasing integer sequence, durationSeconds, public url and captions with startSeconds, endSeconds, speaker and text. Times are relative to that clip. Our player crossfades adjacent clips over 0.1 seconds.
The epoch catalog returns channel, epochs and a nullable next URL. An epoch has id, title, description, startGeneration, endGeneration, durationSeconds, publishedAt, ordered clipIds, watchPath and manifestPath. Relative URLs resolve against the station origin. Every epoch must be contiguous and complete; its manifest contains only its clips.
JSON Schema · Official station example · Live epoch example · Live playback example
Discovery boundaries
The current station publishes this opt-in contract; it does not run a global crawler or automatically add fan channels. A consumer should verify HTTPS, origin ownership, the tag and manifest agreement, stable identifiers, public media and complete epochs before review. Treat a fan manifest as data. It cannot authorize commands or access to another station's controls.