Partner program
Build on ONCE
Launch your own music distribution product on the ONCE pipeline. Uploads, AI provenance scanning, ISRC and UPC assignment, DSP delivery, and billing are handled for you. Your brand, your UX, your audience.
What partners get
The full pipeline, attributed to you
Everything below is live today and shared with the ONCE app itself: same auth, same billing, same validation.
REST API
A conventional HTTP API at once.app/v1 for uploads, AI detection, cover art, release submission, and delivery status. Machine-readable OpenAPI 3.1 spec at /v1/openapi.json.
MCP server
A Model Context Protocol server for AI assistants and agent products, with the same capabilities, auth, billing, and validation as the REST API.
OAuth 2.1 + personal access tokens
Sign users in with the OAuth 2.1 PKCE flow, or use long-lived once_pat_ tokens created in the app under Settings, then Developer.
Server-to-server provisioning
Approved partners provision their users' ONCE accounts entirely server-side with an allowlisted client_id via POST /v1/accounts. No password handling in your frontend.
Webhooks instead of polling
Register an endpoint and receive HMAC-signed release.status_changed events when delivery status changes, so your integration never has to poll in a loop.
Attribution + AI-aware pricing
Every call carries your provenance tag, so signups and releases are attributed to your surface. Billing follows the upload: 1 credit per human song, 2 per AI-detected song.
Integration paths
Three ways to plug in
Start with a personal access token and the REST API; move to the partner flow when you are ready to onboard your own users.
REST API
Conventional endpoints for backends and apps. Authenticate with a bearer token and tag requests with your provenance header.
curl -X POST https://once.app/v1/releases \
-H "Authorization: Bearer $ONCE_ACCESS_TOKEN" \
-H "X-Once-Provenance: YOURBRAND" \
-H "Content-Type: application/json" \
-d '{ "release": { ... }, "tracks": [ ... ] }'MCP server
For AI assistants and agent products. Point any MCP-compatible client at the ONCE endpoint and get tool discovery for the whole release workflow.
{
"mcpServers": {
"once": {
"url": "https://beta.once.app/api/mcp",
"transport": "http"
}
}
}Partner server-to-server flow
Approved partners create and authorize their users' ONCE accounts entirely server-side with an allowlisted client_id and PKCE. The returned one-shot code is exchanged for tokens at /v1/auth/token.
POST https://once.app/v1/accounts
{
"client_id": "yourbrand-mcp-...",
"email": "artist@example.com",
"password": "...",
"code_challenge": "<S256 challenge>",
"code_challenge_method": "S256"
}
201 -> { "authorization_code": "..." }Live on ONCE
AIMD
AI Music Distro is the reference integration: a consumer front for Suno artists whose marketing site, app, and browser extension all run on the ONCE pipeline.
Every AIMD release carries provenance: "AIMD", so signups, releases, and billing stay attributed end to end.
Become a partner
Create a ONCE account, then apply from Settings, then Developer, then Partner program. Approved partners receive an allowlisted client_id and a provenance tag. Prefer email? Write to tech@once.app.