Ordinary text requests
An initial text request does not promise replay of the original response or exactly-once execution. Timeouts, reloads, interrupted streams and SDK network errors do not prove the provider never executed.
- Retain the transport ID and any returned consumption ID.
- Inspect execution and financial state in My requests.
- Only after confirmed non-acceptance should the application/user explicitly decide to issue another request.
Model examples disable automatic SDK POST retries. Adding Idempotency-Key to every text request does not create a universal safe-replay guarantee.
Operations with explicit idempotency
Use Idempotency-Key for media, orders, budgets or compliance only when that endpoint’s contract supports it. Persist the original key and parameters and reuse them for recovery of the same operation. Changes to identity, profile, quantity, amount or price version can conflict; do not bypass 409 with a random new key.
Transport, consumption and provider/task/operation identifiers are separate. Settlement, release and refunds follow their own rules; cancelling a UI action does not erase actual usage.
Next action
| Known state | Action |
|---|---|
| Definitely not accepted | Correct conditions and explicitly submit a new request |
| Accepted and running | Query the original request/task |
| Unknown outcome | Keep original identifiers and reconcile before executing again |
| Delivered, billing pending | Keep the output and query the original bill; do not assume free usage |