Visa CLI · Music Generation · NEW

Every track leaves a receipt. Every rights claim is in the envelope.

A music-gen merchant on the Visa CLI mints one hive-vcr-1 receipt per generated track. Source-corpus class, training rights posture, and likeness or voice-print attestation are co-signed before the audio returns.

Reference vendors: Suno · Udio · Stable Audio
Envelope · music generation

The fields the operator co-signs before this call returns.

Every field below is co-signed by the operator with ML-DSA-65 and countersigned by Hive. Absence is not a default. Absence is a verification failure. The merchant cannot return the call's result without the receipt; the receipt cannot exist without these fields.

SIGNED FIELDS

Music Generation · attestation fields

model_classsuno-v4 | udio-1.5 | stable-audio-2
corpus_classlicensed | public-domain | mixed
voice_print_consentnone | consented | denied
rights_classcommercial | non-commercial | personal
duration_secondsco-signed
settlementUSDC · Base
countersignatureHiveTrust · ML-DSA-65
verificationoffline
What this unlocks

Three places this category needs a receipt yesterday.

USE CASE

Sync licensing for ads

A generated track destined for a national broadcast carries the rights-class attestation in the same envelope as the audio hash. The buyer's compliance team verifies once, offline.

USE CASE

UGC platforms

Per-track receipts let a platform prove it knew, at generation time, whether the training corpus included a flagged artist. Knowledge is provable, not asserted.

USE CASE

Royalty distribution

Receipts feed a downstream royalty engine because the corpus_class field tells the engine which pool to credit. No reconciliation meeting.

Adoption

One endpoint. One envelope. No Hive dependency in your inference path.

A music generation operator adopts hive-vcr-1 by appending the receipt envelope to the response and exposing a public verification key. Hive's countersignature is a sidecar; it does not sit on the critical path. If Hive disappears, the operator's receipts remain verifiable against the operator's own key.