Suede LabsRoyalty Rails
AI Royalties Guide

AI royalties need proof, terms, use, splits, and settlement.

AI royalties are payments tied to a licensed or otherwise compensated use of creative work in an AI workflow. They become programmable only when the system can identify the work, evaluate the terms, record the covered use, and route the agreed value.

By Jason Colapietro (Johnny Suede) · Founder & CEO of Suede Labs AI

Direct Answer

What are AI royalties?

AI royalties are not one new statutory royalty category. The phrase describes compensation connected to AI-related uses of creative work: licensing material for training or generation, using a work in an AI-assisted product, authorizing derivatives, or sharing revenue from licensed outputs. Whether payment is owed depends on the relevant rights, contracts, licenses, platform rules, and facts.

You cannot automate royalties on content you cannot verify. A payment rail needs a reliable asset identity, a party authorized to set terms, a defined price or share, a record of the event those terms cover, and valid destinations for the money.

Rights Map

AI royalties are not one revenue stream.

A single song can contain separate rights in the musical composition and the sound recording, and those rights may have different owners and license paths. Voice, likeness, samples, and other source material can add more permissions. A programmable system should preserve those distinctions instead of flattening every contributor into one generic owner field.

The U.S. Copyright Office's guidance for musicians explains the separation between a musical work and a sound recording. Programmable royalty logic can make an agreed split easier to execute, but it does not decide who legally controls a disputed right.

The Stack

The five prerequisites for programmable AI royalties

1. WorkA stable identifier points to the exact asset or version involved.
2. AuthorityThe party setting terms has a documented claim and contributor context.
3. LicensePermitted uses, prices, attribution, and derivative conditions are explicit.
4. EventA covered license, use, sale, or revenue event is recorded.
5. SplitRecipients, percentages, fees, currencies, and payout addresses are defined.
SettlementThe supported rail transfers value and preserves a transaction record.
ReconciliationParticipants can inspect what happened and resolve exceptions.

Proof of creation and content provenance support the first two prerequisites. Programmable IP makes the license and split legible to software. Settlement is the last step, not the whole system.

Use Cases

What programmable royalty rails can automate

  • License fees: collect a fixed amount when a buyer or agent accepts published terms.
  • Collaborator splits: route an agreed payment across named recipients.
  • Derivative revenue shares: preserve parent-child relationships and calculate defined shares.
  • Platform or protocol fees: apply disclosed fees that were part of the accepted transaction.
  • Audit records: keep the license, event, split, and settlement connected for reconciliation.

Story's official Royalty Module documentation is one public example of software that maps derivative relationships, revenue shares, vaults, and claims. It also illustrates an important boundary: a payment still has to enter the supported system before the module can distribute it.

Boundaries

What royalty code cannot solve by itself

A smart contract cannot detect every off-platform use, verify that a claimant cleared every sample, decide whether an exception such as fair use applies, force an unsupported platform to report an event, or guarantee that a transaction will earn money. It can faithfully execute the inputs and events the connected system recognizes.

That is why this cluster starts with the operational gap around copyright, moves through proof and provenance, defines permissions as programmable IP, and ends with royalty settlement. Skipping straight to payments produces a precise ledger for an imprecise claim.

This page is educational and does not provide legal, financial, or investment advice.

Creator Ownership

Start with the hub for the complete ownership system.

 Programmable IP

See how proof, provenance, permissions, and payment fit together.

 Why Copyright Alone Falls Short

Understand why legal rights still need operational infrastructure.

 Suede IP Registry

Inspect the public registry and its supported ownership records.

 Proof of Creation

Connect the work to a creation record before defining payment logic.

 Agentic Commerce

See how agents discover terms and pay through supported rails.