Niche DSP
Partner sandbox program · June 2026

Licensed music streaming, delivered as one API.

Catalog, streaming infrastructure, and royalty accounting — so any platform can offer music inside its own app. Your engineering team integrates against one REST API and goes from zero to streaming in weeks, not years.

Request a sandbox key See how it works
api.dsp.audio / v1 — sandbox
POST /v1/auth/token 200 · 12ms
GET /v1/catalog/search?q=warm+soul 200 · 38ms
POST /v1/stream/authorize 200 · 4ms
GET /v1/stream/manifest/{session} 200 · <5ms edge
Indie catalog via standard distributor feeds· AES-128 HLS encrypted streaming· 20% platform / 80% to rights holders· One API · any player
Why Niche DSP

Three barriers stand between a platform and streaming music.

A company that wants to offer music streaming today faces years of work before a single track plays. Niche DSP removes all three barriers so your team can ship instead of negotiate.

Barrier 01

Label licensing takes years.

Negotiating direct deals with the major labels is an 18–24 month process before you can legally stream a catalog. Niche DSP sidesteps this entirely by integrating standard distributor feeds from day one — the same mechanism every modern DSP uses.

18–24 months → day one
Barrier 02

Infrastructure is a multi-year build.

Transcoding, encryption, key delivery, a global CDN, and scale represent millions and years of engineering. Niche DSP is a finished platform that your team calls through one REST API.

$5–10M build → one API call
Barrier 03

Royalty accounting never ends.

Qualified-play calculation, statements, payments, fraud detection, and audits are an ongoing operational burden. Niche DSP handles royalty accounting end to end, from the raw play event to the rights-holder statement.

Ongoing ops → handled
How it works

Four responsibilities. One backend.

Niche DSP runs the full path from raw label delivery to a track playing in your player — and captures every play along the way for royalties and reporting.

Ingest

Catalog in, validated.

Catalog arrives via standard distributor feeds. Every track is registered, fingerprinted, validated, and de-duplicated on identifiers like ISRC — redeliveries update, never duplicate.

Derive

Source to stream-ready.

Source WAV/FLAC is transcoded to multi-bitrate HLS with AES-128 encryption — just-in-time on first play, or pre-transcoded for popular catalog. Tracks that are never played are never transcoded.

Deliver

One access chokepoint.

Every stream passes through one access-decision chokepoint. On approval, a signed manifest and session-bound key unlock playback at the edge in under 5ms. Decision and enforcement are the same place.

Track

Every play captured.

Every play start, heartbeat, skip, and seek is captured as an append-only event — feeding qualified-play royalty calculation, fraud detection, and rights-holder reporting. The data is always yours to query and export.

Architectural invariant One-API litmus test

The boundary that keeps your business yours.

Niche DSP Core is mechanism, not product domain. It knows assets, identities, policies, deliveries, and events. It does not know about labels, releases, royalties, or playlists — those live in your management middleware.

You keep absolute authority over billing, subscriptions, identity and login, catalog curation, and reporting. Niche DSP Core reads only the entitlement you assert and enforces the policy you set.

  • Tenant is resolved from your API key — never passed as a parameter
  • Your product plane owns subscriber identities and billing entirely
  • Enforced retraction kills in-flight streams within seconds of a takedown
  • One public API — your team integrates exactly as any tenant would
// HEADLESS MULTI-TENANT SUBSTRATE
Three planes, cleanly separated
Mechanism below, your brand and business rules above.
✓ Boundary enforced at the API key
Plane 1
Your app & player
Plane 2
Niche DSP Core
Plane 3
Your middleware
Enforced at the edge
Tenant scoping
All access flows from the Bearer credential
enforced
Enforced retraction
In-flight streams terminate on non-servable state
enforced
Plainly answered

Questions we get.

Have integration questions or licensing terms to review? Write to hello@nichedsp.com.

What catalog can a partner stream, and from when?
+

Niche DSP integrates content from independent distributors via standard feeds. The catalog is deliberately indie-focused — Niche does not pursue major-label deals, and major-label content is not part of the offering. Partners get the full curated indie catalog from day one. Niche pays distributors per standard rate cards and handles the §115 mechanical obligation directly at the statutory rate.

What content protection is used at the edge?
+

AES-128 HLS with session-token-bound signed manifest URLs and key delivery handled at the edge. This is the same approach the major streaming platforms use and is confirmed acceptable in label licensing context. It plays natively on every HLS-capable device — iOS, Android, web, smart TV, automotive — with no additional DRM enrollment required.

How does the integration model actually work?
+

You integrate the Niche DSP REST API into your existing application. Niche DSP provides licensing, streaming, and royalty accounting; you provide the user interface, the player, and the subscriber relationship. You already have a mature player — you don't need an app built for you, just a licensed catalog and a streaming API you can call. A single stream-authorize call returns a signed manifest and session token in one round trip.

How does territory and geo-blocking work?
+

Every asset carries a composable access policy evaluated at a single chokepoint. The edge checks the request's country against the asset's territory rule in under 5ms, including per-track per-country rules. If a subscriber's location conflicts with the asset's allowance, the key is withheld and playback never starts.

Where do billing and subscriptions live?
+

Entirely in your product middleware. Niche DSP runs no login, stores no credential, and has no concept of a subscription or payment. You manage payment collection and assert the resulting entitlement to Niche DSP — which reads it, caches it with a TTL, and fails closed if it can't verify. Your commercial logic stays flexible and never bloats the streaming substrate.

How does the revenue model work?
+

20% platform fee, 80% pass-through to rights holders. The 80% flows through distributors on their standard rate cards. The §115 publishing mechanical and performance royalties are paid by Niche directly to the relevant collecting societies, separate from distributor settlement. This is the same shape as every modern DSP — the differentiation is in the consumer product, not in artist economics.

Partner sandbox program · June 2026

Stop re-inventing the streaming stack.

Niche DSP is onboarding a first cohort of distribution partners. Authenticate a user, search the catalog, start a stream, and play a track in your own player — using nothing but the REST API.

What partners get

  • Direct access to the founding engineering team during integration
  • Indie catalog via standard distributor feeds for testing — the same pipeline used in production
  • Zero data egress fees on streaming delivery
  • Royalty reporting and rights-holder log access on the Pro tier
Request a sandbox key
// INTEGRATION PATH

From key to first stream

01Tell us your platform, player, and target territories. We issue a sandbox API key.
02Authenticate a user, search the catalog, and call stream-authorize against the live sandbox.
03Play a track in your own player end to end, then scope a production integration and LOI.
Ready to evaluate the API?hello@nichedsp.com