Skip to content

Media Onboarding

Onboard your recordings, publishing and NILV to the Sureel Platform.

Contact Us
Releases
Rights & AI Permissions
rising_tempest_master.wav
Uploading
new_dawn_master.wav
Uploading
artist_voice_sample.wav
Uploading

What is Media Onboarding?

Media onboarding is how artists, labels, and publishers register their recordings, compositions, and NILV on the Sureel Platform. It is the foundation for setting AI permissions, enforcing guardrails, and tracking attribution. The process covers:

  • Preparing media: audio, lyrics, images and associated metadata
  • Choosing an onboarding method: Frontend, API, OpenPlay, CSV/JSON, or DDEX
  • Registering media: with rights declarations and AI permissions
  • Post-onboarding management: ongoing uploads, monitoring, and attribution

Supported Media & Metadata

What you can onboard and the data we need to register it properly.

Supported Media Types

Audio

Examples: Songs, stems, instrumentals, a cappella

Formats:MP3WAV

Lyrics

Examples: Song lyrics with optional timing data

Formats:Texttime-synced

Images

Examples: Album art, promotional images, artist photos

Formats:JPGPNG

These fields are mandatory for every asset you onboard.

Required
TitleThe title of the track, composition, or media asset
CreatorsArtist, lyricist, and/or composer names associated with the work

Onboarding Methods

Choose the method that best fits your catalog size, technical setup, and workflow.

MethodBest For
Frontend ReleaseIndividual artists or small catalogs
API IntegrationLarge catalogs / automation
OpenPlay IntegrationOpenPlay users
CSV / JSONSmall/medium catalogs
DDEXIndustry-standard workflows

The simplest way to onboard media. Use the Sureel web app to create a release, upload your media files, and fill in metadata through a guided form.

Steps

  1. Navigate to Releases → Create New Release
  2. Enter your release metadata (title, artists, release date, etc.)
  3. Upload audio files (MP3 or WAV), cover art, and optional lyrics
  4. Declare whether any track is a cover song, and set your rights declarations and AI permissions
  5. Review and submit your release for processing

Best for:

Artists managing their own releases, small labels with a handful of releases, or anyone who prefers a visual interface over technical integration.

For programmatic access to media onboarding. Use the Sureel REST API to automate uploads, manage metadata, and handle large catalogs at scale.

Step 1: Authenticate

Obtain an access token using Auth0 client credentials:

bash
curl --request POST \
  --url https://sureel.eu.auth0.com/oauth/token \
  --header 'content-type: application/json' \
  --data '{
    "client_id": "<Your-Client-Id>",
    "client_secret": "<Your-Client-Secret>",
    "audience": "https://api.sureel.ai",
    "grant_type": "client_credentials"
  }'

Step 2: Generate Upload URLs

Request signed upload URLs for your media files:

bash
curl -X POST https://api.sureel.ai/v1/files/generate-upload-urls \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "files": [
      { "fileName": "rising_tempest_master.wav", "contentType": "audio/wav" },
      { "fileName": "cover-art.jpg", "contentType": "image/jpeg" }
    ]
  }'

Step 3: Upload Files

Upload each file to its signed URL:

bash
# Upload file to the signed URL returned from generate-upload-urls
curl -X PUT "<signed-upload-url>" \
  --header 'Content-Type: audio/wav' \
  --data-binary @rising_tempest_master.wav

Step 4: Create Collection

Create a collection (album/single/EP) with your uploaded files and metadata:

bash
curl -X POST https://api.sureel.ai/v1/ai/artist/upload-artwork \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "collectionName": "My Album",
    "releaseDate": "2025-06-15",
    "tracks": [
      {
        "trackTitle": "Rising Tempest",
        "isrc": "USRC12345678",
        "artists": ["Artist Name"],
        "labels": ["Label Name"],
        "genres": ["Electronic"],
        "fileId": "<file-id-from-upload>"
      }
    ],
    "coverArt": "<cover-file-id>",
    "aiInfluence": "Generated without AI"
  }'

Step 5: Verify

Check your collections to confirm the upload:

bash
# Check upload/processing status
curl https://api.sureel.ai/v1/ai/artist/collections \
  --header 'Authorization: Bearer <token>'

If you already use OpenPlay for your catalog management, Sureel offers a fully managed integration. Your existing catalog flows directly into the Sureel Registry with no additional work.

Steps

  1. Contact Sureel to set up your OpenPlay integration (info@sureel.ai)
  2. Select which OpenPlay media you want to register with Sureel
  3. Generate OpenPlay API keys to grant Sureel access to your catalog
  4. Your catalog is automatically synced to the Sureel Registry
  5. Ongoing updates are handled automatically, with no manual uploads needed

Fully Managed

The OpenPlay integration is fully managed by Sureel. Once configured, your catalog stays in sync automatically with no ongoing maintenance required.

Download a CSV or JSON template, populate it with your metadata, and upload it along with your media files. Ideal for catalogs where you have metadata in spreadsheets.

Steps

  1. Download the CSV or JSON template
  2. Populate the template with your catalog metadata (one row/object per track)
  3. Prepare your media files in a folder with filenames matching the template
  4. Send the completed template and media files to Sureel (info@sureel.ai)
  5. Sureel processes and ingests your catalog into the registry

For organizations using the DDEX standard for digital supply chain metadata. Share your DDEX-compliant XML metadata alongside your media files with us via email or directly through our DDEX API endpoint.

Steps

  1. Prepare your DDEX-compliant XML metadata files following the ERN (Electronic Release Notification) standard
  2. Ensure file references in the XML match the actual filenames of your media files
  3. Share your submission with Sureel via email (info@sureel.ai) or via the DDEX API endpoint
  4. Sureel validates and ingests your DDEX submission into the registry

DDEX Standards Supported

We support ERN (Electronic Release Notification) for new releases. Contact us if you use other DDEX message types such as MLC (Musical Works Licensing) or DSR (Sales Reporting).

Label vs Publisher Requirements

Labels and publishers have different media types and metadata needs. Here's what to prepare for each.

AspectLabelsPublishers
Primary MediaFull tracks + optional stems (vocals and instrumentals)Composition data (song title, composers with IPI, publishing splits)
Required MetadataTitle, artists, ISRC, release date, label nameSong title, composers with IPI numbers, publishing splits, PRO affiliations
Supplementary DataGenre, tempo/key, album art, rights splitsISWC, territory rights, sub-publisher information
Preferred FormatsWAV or MP3 for audio; JPG/PNG for artworkMIDI, MusicXML, DDEX preferred over PDFs
Onboarding MethodsAll methods available (Frontend, API, CSV/JSON, DDEX, OpenPlay)API for bulk automation, DDEX, or CSV/JSON

For Labels

  • Full tracks + optional stems (vocals and instrumentals)
  • Core metadata: title, artists, ISRC, release date
  • Supplementary: genre, tempo/key, album art, rights splits

For Publishers

  • Composition data: song title, composers with IPI numbers
  • Publishing splits and PRO affiliations
  • Preferred formats: MIDI, MusicXML, DDEX (over PDFs)

Rights & AI Permissions

Declare your rights and set permissions for how your media may be used in AI training and generation.

Rights Declarations

  • Master ownership and licensing terms
  • Territorial restrictions for distribution
  • Exclusive vs. non-exclusive rights declarations
  • Songwriter and composer credits with IPI numbers
  • Publishing splits between multiple parties
  • Mechanical and synchronization rights
  • Cover song declaration and original work references
  • Recording rights vs. underlying composition ownership
  • 100% composition clearance required to opt in for AI training and generation
  • Name: stage name and legal name
  • Image: photos, album art, visual assets
  • Likeness: visual representation and persona
  • Voice: spoken recordings, vocal stems, singing voice

AI Permissions

Choose whether AI companies can train on your media, and whether they can generate with it.

Opt-In for AI Training

Allow AI companies to train on your media. Opted-in media is tracked with full attribution, so you're credited when your work shapes an AI output. A composition can only be opted in once 100% of it is cleared.

Opt-Out of AI Training

Prevent your media from being used in AI model training. Your assets are registered in the Do-Not-Train registry, and AI developers can check this registry before training to ensure compliance with your wishes.

Usage rules

Fine-tune how AI companies may use your media: a maximum influence per output, a minimum credit for style requests, artists and genres AI may not blend you with, and whether your cover art and lyrics can be used.

How closely AI can sound like you

Set how closely AI-generated music may resemble your work, from Nothing like me to Very close. Attribution is tuned to match.

Post-Onboarding

What happens after you upload your media, and how to manage it going forward.

Processing Pipeline

After your media is submitted, it goes through these stages:

01Uploading

Media Validation

Your uploaded media and metadata are validated for format compliance, completeness, and data integrity.

02Matched

Secure Migration

Validated media is securely transferred to the Sureel Registry with encryption at rest and in transit.

03Registered

Registry Indexing

Your media is fingerprinted and indexed in the registry, enabling permissions enforcement and attribution analysis.

Ongoing Management

After onboarding, you can continue uploading new media and managing your catalog:

Scheduled API calls: Automate ongoing uploads with cron jobs or CI/CD pipelines
Manual uploads: Use the web app or CSV/JSON for ad-hoc additions
Metadata updates: Update rights, splits, and preferences via the API or web app