Labels & managers
Explore scoped roster, campaign, and operational workflows for authorized entities.
BUILD ON BANDRUPTION
Build your music product on Bandruption
Connect your own frontend to the events, commerce, fan-engagement, and agent infrastructure behind Bandruption through current APIs, MCP, and typed contracts.
A guided look at the command-center experience
OPENAPI · MCP · TYPES
GET /api-docs
MCP preview → confirm
SDK typed contracts
WHO IT IS FOR
Infrastructure for music operators and product teams
Built for labels, managers, venues, and music-app teams: pick the interfaces you need and the artists or industry entities you manage, and start building.
Venues & promoters
Connect event, ticket, and fan workflows to an owned customer experience.
Music applications
Build a differentiated frontend on current platform contracts and music infrastructure.
CURRENT INTERFACES
Choose the contract that fits the job
Current paths and schemas live in the public API reference at bandruption.fun/api-docs.
OpenAPI / REST
Inspect the current API reference at bandruption.fun/api-docs before implementing a request.
MCP
Connect agents to music-specific tools that use scoped preview and confirmation patterns.
Typed contracts
Use the current TypeScript package and shared contracts where their published surface fits the integration.
Scoped access
API-key and OAuth paths follow their documented account and entity permissions.
ARCHITECTURE
Your experience, typed interfaces, Bandruption systems
Keep the customer-facing product you want while using current music-specific platform capabilities behind it.
LAYER 01
Your frontend
Web, mobile, internal operations, or an agent experience owned by your team.
LAYER 02
API, MCP & contracts
Documented interfaces carry authorized requests and structured results.
LAYER 03
Music infrastructure
Events, tickets, commerce, fan engagement, and current agent tools.
AUTHENTICATED REQUEST SHAPE
Keep credentials outside the example
Use the current reference to choose the endpoint and request body. Send the access token through the documented authorization header and handle non-success responses explicitly.
const response = await fetch(endpoint, {
headers: {
Authorization: `Bearer ${accessToken}`,
"Content-Type": "application/json"
}
});
if (!response.ok) throw new Error("Request failed");PARTNER ONBOARDING
Pick your scope, get your keys, build
You control your own integration scope from the admin dashboard — it covers the industry and artist entities you administer, nothing more, nothing hidden.
01
Select your entities
In the admin dashboard, choose the artists and industry profiles you administer that the integration should cover.
02
Get your credentials
Create API keys or OAuth access scoped to exactly the entities you selected.
03
Build against the live reference
Implement against the current API reference, MCP guide, and typed contracts.
SECURITY & SCOPE
Access follows identity, entity, and action
Access is limited to the credentials and entity you grant; agent actions preview first and require confirmation.
Authenticated identity
Requests use the documented API-key or OAuth path for the integration.
Entity-aware permissions
An operator or integration may act only in the entities and capabilities it is granted.
Action confirmation
Tools that change data preview the proposed action and require a confirmed call.
Questions, answered
It begins with the currently documented APIs, MCP tools, and typed contracts that fit the agreed use case. Commercial scope, support, and any additional delivery are defined separately.
Yes, that is a core integration shape. Your frontend remains yours while it calls the authorized Bandruption interfaces selected for the project.
Current events, tickets, and eligible merchandise systems can be evaluated during scoping. Availability still depends on the documented interface, entity access, and commercial terms.
Exactly the scope you select in the admin dashboard: the industry and artist entities you are an admin on. You set it yourself — no mystery, no blanket access.
Yes. Your frontend, brand, and product stay yours — Bandruption provides the music infrastructure behind them through the documented APIs, MCP tools, and typed contracts.
Start with the live interfaces
Inspect the MCP guide and API reference, then bring a specific music-product outcome to the integration conversation.
