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.
OPENAPI · MCP · TYPES
GET /api-docs
MCP preview → confirm
SDK typed contracts
WHO IT IS FOR
Infrastructure for music operators and product teams
Start with the interface and entity scope you need; discovery defines the integration rather than promising a universal white-label package.
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
The public reference is the source for current paths and schemas; marketing does not invent endpoints, limits, or maturity promises.
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
Scope before implementation
Discovery establishes the use case, entities, data boundary, access method, and commercial conversation. No fixed SLA or package is implied.
01
Define the outcome
Identify the customer journey, operating roles, and Bandruption systems needed.
02
Agree the boundary
Confirm identity, entity scope, data access, and approval requirements.
03
Build against current docs
Validate the integration against the live reference and agreed environment.
SECURITY & SCOPE
Access follows identity, entity, and action
The documented model limits operations to the credentials and entity context supplied; agent mutations keep their confirmation boundary.
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.
Mutation confirmation
MCP mutation tools preview the proposed action before the 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.
No such blanket access is promised. Identity, entity, and capability scope constrain each integration; confirm the exact data boundary during onboarding.
No. BaaS supports building your own product on available infrastructure, but branding, implementation, support, SLAs, and commercial terms require their own agreement.
Start with the live interfaces
Inspect the MCP guide and API reference, then bring a specific music-product outcome to the integration conversation.