Developer documentation
How agents safely retry BLERBZ mutation requests.
Mutation endpoints that create, cancel, or enqueue work should accept an Idempotency-Key header. The key should be unique per logical operation and reused only when retrying the same request after a network failure, timeout, or 5xx response.
A duplicate key with the same method, path, and normalized body should return the original operation result when available. A duplicate key reused for a different request should return a typed 409 IDEMPOTENCY_KEY_REUSED error.
Agents should generate stable keys such as blerbz:<workflow>:<uuid>, persist them for the retry window, and avoid using one key for different prompts, users, jobs, or media operations.