VoxEmpire
Every track and beat on VoxEmpire ships with a documented rights chain. This page explains what that means, what each field captures, how producers fill it, and how the receipt travels across the web.
A rights chain is the structured record of how a release was made. Not a sticker. Not a marketing claim. The actual record — stored as JSONB in the database, rendered as a public page, exported as JSON for downstream automation, and indexed as schema.org structured data for search engines and AI assistants.
Every chain has five fields. Each one is required. Together they answer the question that 2026 distribution increasingly asks: can you prove where this came from?
Every human on the work — name + role. Vocalist, producer, mixer, lyricist, cover artist. Short list for most independent releases; that is fine. What matters is that it is explicit.
Every AI tool that touched the work — name + the part it touched. Suno arranged the instrumental. Claude drafted lyric ideas. Replicate generated the cover art. The point is granularity: not 'used AI' but 'this tool, this part, this version.'
The structural breakdown — intro, verse, chorus, bridge, outro — each with its source (the contributor or tool that produced it), status (original / AI-assisted / licensed), and time range in seconds. This is what powers the live receipt on /listen and the click-to-seek behavior.
Signed by + signed at. The legal name of the person standing behind the chain, and the date they did. Functions as the human attestation that the rest of the record is accurate.
Title and kind (track or beat). Lets the receipt render with the right semantics — MusicRecording schema for tracks, CreativeWork for beats.
The producer rights wizard on /upload captures all five fields inline as part of the beat upload flow. Contributors and AI tools are repeater rows. A structure preset (simple loop or verse/chorus) auto-generates element ranges from the audio duration the producer just uploaded. The warranty defaults to the producer's profile name.
The data is sanitized server-side (defensively — every field is shape-checked, length-clamped, dropped on anomaly) and persisted as JSONB on the beat row. From that point, every receipt surface lights up automatically — no extra step from the producer.
A receipt that lives only inside one platform is a sticker. A receipt that has a URL, exports as JSON, indexes as structured data, and unfurls as a social card is an artifact. We built the second kind.
voxempire.app/receipt/<slug>. Embeddable in contracts, paste-able in press kits.A rights chain on VoxEmpire is a structured record of how a track or beat was made — every contributor, every AI tool used (with the part of the work it touched), every time-ranged element marked original/licensed/AI-assisted, and a signed warranty. Stored as JSONB, rendered as a public receipt page, exported as JSON, and indexed as schema.org structured data. Every release ships with one.
Five fields. (1) Contributors — name + role for every human on the work. (2) AI tools — name + what part of the work each tool touched. (3) Elements — the structural breakdown (intro, verse, chorus, bridge, outro) with source, status (original / AI-assisted / licensed), time range in seconds, and optional detail. (4) Warranty — signed by + signed at date. (5) Subject metadata — title and kind (track or beat).
The producer rights wizard on /upload captures all five fields inline as part of the beat upload flow. Contributors and AI tools are repeater rows. A structure preset (simple_loop or verse_chorus) auto-generates element ranges from the audio duration. The warranty defaults to the producer's profile name. The data is sanitized server-side and persisted as JSONB. The /receipts directory, the BeatReceipt strip on /explore, the /receipt page, and the JSON-LD all light up automatically — no extra step.
Every documented chain has a public URL at /receipt/<slug>. It is indexed in the sitemap, listed in the /receipts directory, emits schema.org JSON-LD (MusicRecording for tracks, CreativeWork for beats) for search engines and AI answer surfaces, can be exported as JSON or copied to clipboard for inclusion in contracts and press kits, and is rendered as the OG card when the receipt URL is shared. The receipt is designed to travel.
Because a PDF is opaque to search engines, AI assistants, and downstream automation. A structured chain rendered as JSON-LD lets Google AI Overviews, Perplexity, ChatGPT, and Claude answer questions like 'who made this track' or 'what AI tools were used on this beat' by reading the chain directly. The JSON export option exists for the human-facing use cases (contracts, press kits, label compliance tools) where a portable artifact is needed.
Then the AI tools array on the chain is empty. The receipt page renders 'None — fully original' and the structured data omits the mentions field. The rights chain is still required; it just documents that the entire work is original to the contributors listed.
Yes. Producers can refine their chain through the wizard after upload — adding contributors, marking elements as licensed when clearance comes through, updating the signedAt date. The receipt page always renders the latest version. Historical versions are not yet surfaced publicly but are retained in the database for audit purposes.
Every SoundVox generation auto-creates a rights-chain receipt like the ones described above. Paste your lyrics, pick a genre, and the receipt ships automatically.