Documentation for coding agents

Use Kasty documentation as a versioned contract graph. Prefer raw machine artifacts for schema work and narrative guides for operational intent. Never infer product availability from an endpoint name alone.

Discovery order

1. Read /music-delivery-status.json for reviewed channel status.
2. Read /openapi/music-delivery-v1.yaml for operations and response contracts.
3. Read /schemas/ artifacts for exact component schemas.
4. Read validated examples under /examples/music-delivery-v1/.
5. Use Music Delivery quickstart for required ordering and human handoffs.

Safety boundaries

Do not place bearer credentials, signed URLs, storage keys, customer manifests or real identifiers into generated code or prompts. Do not manufacture legal acceptance, payment acknowledgement, sender activation, video-use permission or DDEX conformance.

Status-aware implementation

AVAILABLE, LIMITED_PILOT, BILATERAL_ONBOARDING, PLANNED and UNAVAILABLE are functional truth. Build only against the organization’s activated cohort. A machine credential cannot complete a human agreement action.

Conflict handling

When narrative and raw contract disagree, stop automated mutation, retain both source URLs and content hashes, and report the mismatch. The raw versioned OpenAPI or schema controls request shape; Kasty must resolve any operational-semantic conflict.

Useful artifacts

Start with /llms.txt for a concise index and /llms-full.txt for the public narrative compilation. The build manifest lists source and artifact hashes so agents can detect drift without scraping frontend chrome.