Casset artist integrations
Your artist profile should work everywhere.
Most artists have their music, visuals, demos, links, and private drops scattered across different apps. Casset gives approved tools one safe place to read from, so your artist world can power websites, fan experiences, AI assistants, label tools, and new music apps without you rebuilding it every time.
Approved app reads Connor's Casset200 OK · 112 KB"handle": "connor", "name": "Connor James", "isVerified": false, "url": "https://casset.fm/connor", "counts": { tracks: 58, visuals: 10, releases: 1 }, "tracks": [{ "id": "connor-lose-you", "title": "lose you", "kind": "ORIGINAL" }], // +57 more "endpoints": { ask: "https://casset.fm/api/agents/artists/connor/ask" }
This is what an approved app can read from Casset: the artist profile, tracks, visuals, releases, and useful links.
The simple version
An API is just a safe door for approved tools.
Imagine your Casset is a house for your music. Inside are your songs, visuals, demos, private drops, and the story behind your work. An API is a door that lets approved tools knock and ask for the right things. For example: what songs does this artist have, what visuals belong to this track, what is public, and what can fans unlock?
You keep the house
Your music, visuals, demos, and drops stay organized inside Casset.
Tools ask for permission
Websites, AI assistants, labels, and fan apps can read the parts you allow.
You avoid rebuilding
Instead of uploading the same story everywhere, Casset becomes the source.
Why this matters
Streaming plays the song. Casset explains the world around it.
Spotify and Apple Music are great for listening. Casset is for everything around the music.
A streaming link tells people what to play. It usually does not explain the demos, visuals, samples, private drops, alternate versions, fan moments, or the story behind the song. Casset keeps that context in one place so approved tools can use it.
Streaming platforms
- · song title
- · cover art
- · artist name
- · duration
- · play button
Casset
- + songs and demos
- + visuals and behind the scenes
- + private drops
- + alternate versions
- + artist story and fan experiences
Artist control
Approved tools can read your world. Random scrapers cannot.
Think of the Casset API like a locked door to your artist profile. You decide who gets a key. Public things can stay public. Private drops, unreleased songs, fan data, payments, and raw files stay private unless you allow access.
The goal is simple: help good tools understand your music without giving everyone your private files.
You choose what is public
Your public profile, public tracks, public visuals, and approved links can be used by outside tools.
Private work stays private
Unreleased songs, private drops, raw files, fan data, payments, and drafts are not exposed by default.
Access can be approved
You can let trusted apps, agents, labels, or partners read the parts of your Casset they need.
Access can be turned off
API keys can be limited, tracked, rate-limited, and revoked.
What tools can read
One artist profile. Many places it can show up.
This is the technical part, but the idea is simple. Casset organizes your songs, visuals, drops, demos, and profile information so approved tools can read them cleanly instead of scraping pages or asking you to upload the same files again.
Available now
/api/agentsLivePublic
What Casset can share
A public list of what the API supports. This helps apps understand how to connect to Casset.
/api/agents/artists/{handle}Private betaAPI key required
Artist profile bundle
The approved artist profile: bio, counts, tracks, visuals, releases, and useful links. Private files, payments, and fan personal data are not included.
· tracks[]Private betaAPI key required
Songs and versions
Track IDs, titles, original songs, AI versions, durations, posters, and basic song info that other tools can reference.
· visuals[]Private betaAPI key required
Visual media
Cover art, behind-the-scenes clips, hooks, and visuals connected to the songs.
/api/agents/artists/{handle}/askPrivate betaAPI key required
Ask the artist archive
Lets an approved AI assistant answer questions using the artist-approved Casset archive instead of guessing from the internet.
/api/agents/releases/{id}/lineageLivePublic · rate-limited
How a song was made
Connects demos, samples, ideas, versions, and finished releases so fans and tools can understand the story behind a track.
Coming next
drops · pre-releaseEmergingPublic
Drops
Pre-release campaigns, private drops, unlocks, and release moments.
momentsEmergingPublic
Fan moments
Fan-submitted clips, memories, and reactions tied to specific tracks or drops.
identities · projectsEmergingPublic
Artist identities
Main profiles, side projects, alter-egos, B-sides, and creative worlds.
casset.fm/{handle}?trackId={id}PlannedPublic
Song deep links
Links that open straight to a specific song, version, or drop inside an artist profile.
What stays private
Not everything needs to be shared. You choose the boundary.
Artists need control. Some things are public, some are for paying fans, and some should never leave the private workspace. Casset keeps those layers separate.
Public
Your public profile, released songs, public visuals, approved moments, and public links.
Fan access
Private drops, paid rooms, holder-only content, unreleased previews, and fan unlocks.
Private
Drafts, raw uploads, private notes, fan personal data, payments, unapproved moments, and analytics.
See the real thing
This is what approved tools can read. No mystery.
Developers can test the public catalog here. Artists do not need to understand the code. The important part is that Casset gives trusted tools a clean, safe way to understand the artist world.
GET /api/agentsThen: fetch any artist bundle
curl https://www.casset.fm/api/agents/artists/connor \ -H "Authorization: Bearer $CASSET_API_KEY"
The discovery call is public — that response above is live. Data endpoints take a server-side key; keep CASSET_API_KEY on your backend.
Why artists should care
Your Casset can power more than one page. It can power a whole system.
Once your music, visuals, demos, and private drops live in one organized place, other approved tools can build on top of it. That means better fan pages, better AI assistants, better campaign tools, and less copying your work from one platform to another.
For artists
Turn your Casset into a home base that other tools can understand.
- Stop rebuilding your artist story in every app
- Keep songs, visuals, demos, and drops connected
- Let approved tools read the right context
- Make private extras easier to sell or share
- Give AI assistants accurate info about your work
AI without the guessing
AI should understand your music from your source. Not from random scraps online.
If an AI assistant only sees a streaming link, it has to guess. If it can read your approved Casset archive, it can answer from your real songs, visuals, demos, drops, and notes. That makes the output more accurate and more useful for fans, teams, and tools.
Your source of truth
The artist-approved version of your profile, songs, visuals, and extras.
Less guessing
AI can answer from your actual archive instead of making things up.
Better fan tools
Fans can ask richer questions and get answers that point back to your work.
Cleaner team workflows
Labels, managers, and collaborators can find what they need faster.
Connected media
Songs, visuals, drops, and demos stay attached to the same artist world.
You stay in control
Private material only becomes readable when access is approved.
Developer example
For developers, it is three simple steps. Find, read, ask.
Artists do not need to run this code. This is what an approved developer, label tool, or AI assistant can do behind the scenes: find what Casset supports, read an artist profile, then ask questions using the artist-approved archive.
public catalog# public, no key required curl https://www.casset.fm/api/agents
artist profile bundlecurl https://www.casset.fm/api/agents/artists/connor \ -H "Authorization: Bearer $CASSET_API_KEY"
ask the archive# ask about a track, release, visual, or drop curl https://www.casset.fm/api/agents/artists/connor/ask \ -H "Authorization: Bearer $CASSET_API_KEY" \ -d '{"question": "what songs has Connor made?"}'
The key is a server-side secret. Developers keep CASSET_API_KEY on their backend and never ship it to the browser. Artists just approve what should be readable.
Your artist home base
Do not rebuild your story on every platform. Give it one place to live.
An artist should not have to re-upload the same songs, visuals, links, demos, and release context into every new tool. Casset can become the organized source that other approved apps read from. You keep the artist world in one place, and the rest of the internet can point back to it.
Organized
Songs, visuals, demos, drops, and extras stay connected.
Reusable
Approved tools can read from the same source instead of asking you to start over.
Controlled
Public stays public, private stays private, and access can be approved or revoked.
Not just another upload
Turn your artist profile into a source other tools can trust.
A streaming link plays a song. A Casset profile can carry the full artist world: songs, visuals, demos, private drops, unlocks, and context that approved tools can safely use.