Reliability and idempotency
Network retries are normal. Every write and delete requires an Idempotency-Key header with at least eight characters.
Talqora stores the request fingerprint and response. Retrying the same request with the same key returns the original response without writing a vector twice or incrementing usage twice.
If you receive 429, honor Retry-After before retrying. Do not retry immediately in a tight loop. For network failures, retry with exponential backoff and reuse the same idempotency key.
Every rate-limited response includes the active budget:
RateLimit-Reset and Retry-After are seconds until capacity becomes available. Successful requests include the first three headers, so clients can slow down before receiving a 429.