Kasty Developers
Build against the public contracts Kasty operates. The first complete program is Music Delivery: catalog packages, direct assets, durable processing, rights instructions and operational recovery for labels, distributors and music partners.
Start with Music Delivery
Use the Music Delivery quickstart to follow one release from strict validation through durable submission, direct asset upload and processing state. The Music Delivery model explains releases, recordings, assets, operational control and the listening-only default for Partner delivery.
Choose the right delivery surface
| Channel | Current availability | Activation boundary |
|---|---|---|
| Partner Console | AVAILABLE | Approved organization and current agreement; sender and write cohort are activated separately. |
| Folder | LIMITED PILOT | Canonical package and manifest through the guided bulk-delivery pilot. |
| CSV / JSON | LIMITED PILOT | Structured adapters normalize into the canonical manifest during guided onboarding. |
| Direct API | LIMITED PILOT | Approved organization, current agreement, scoped credential, active sender and enabled write cohort. |
| ZIP | UNAVAILABLE | Unavailable until bounded staging, archive inspection and malicious-archive controls are production-ready. |
| DDEX ERN | BILATERAL ONBOARDING | Agreed DDEX rights, DPID identities, ERN profile, choreography, transport, mappings and conformance. |
Partner Console is the visual workspace. Guided folder, CSV or JSON delivery is activated for approved workflows. Direct API credentials are scoped to one organization, sender and catalog account. DDEX is a bilateral integration with an agreed profile and conformance process; it is not a public upload endpoint.
Build the complete flow
- Validate the business manifest without creating durable work.
- Submit idempotently and retain the returned batch identity.
- Upload declared assets through object-scoped intents.
- Follow jobs and retries, issues and signed webhooks.
- Keep rights and video use explicit instead of inferring authority from catalog control.
Source of truth
The API reference is generated from the canonical OpenAPI 3.1 contract. Requests, parameters, responses and validated examples are readable inline; raw OpenAPI, JSON Schemas and exact example files remain available for tooling and code generation.
Capability labels such as limited pilot, bilateral onboarding and unavailable are operational boundaries. When a guide and a raw contract differ, stop and use the versioned contract while reporting the documentation mismatch.
For coding agents
Use the agent documentation index or /llms.txt to discover canonical routes. Never place customer payloads, credentials, signed upload URLs or storage keys into prompts, logs or generated examples.