voice_cloning_withdrawn
Self-serve voice cloning is withdrawn (owner decision, 2026-08-18). The four write paths - POST /v1/voice-profiles and the three artifact uploads on a profile, …/sample-recording, …/consent-recording, …/consent-proof - answer this and nothing else; they stay mounted rather than being removed, because 410 says "this existed here and is permanently gone" and a 404 could not be told apart from a typo'd path by an integrator holding a working key. They parse no body and declare no scope, so an old client still POSTing a 20 MB sample is refused before a byte is read and is not sent to fix a key for a capability no key can reach; nothing is stored. Reads are untouched: profiles a tenant already owns still list and read, and an agent pinning an approved one keeps speaking with it. A customer picks a platform voice from GET /v1/voices or asks support about adding one to the roster; the cloning capability itself is now staff-only, through the /admin voice catalog.
Problem shape
Every non-2xx response is an RFC 9457 application/problem+json body. The type URI below is stable and machine-matchable, so branch on the final path segment (the code) and treat the status as redundant confirmation. See the error-handling guide.
{
"type": "https://docs.vocapable.com/errors/voice_cloning_withdrawn",
"title": "…",
"status": 410,
"detail": "…",
"instance": "/v1/…"
}