What Is an Idempotency Key?
An idempotency key is a unique token a client attaches to a request so the server performs the operation at most once, even if the request is retried after a timeout or a network failure. For payments it is the difference between a safe retry and a double charge. Autonomous agents retry aggressively and without a human to notice a duplicate, so an idempotency key on every state-changing call is a baseline requirement for agent-initiated money movement.
Safe retries for machines
A network failure leaves a client unsure whether a request succeeded. A human pauses and checks; an agent retries. Without idempotency, that retry can charge twice, place two orders, or send two payments. With it, the server recognises the repeated key and returns the original result instead of acting again.
It is unglamorous and load-bearing: agent-initiated commerce is a stream of retried, unattended requests, and idempotency is what keeps that stream from doing damage.
Related standards
Questions
Is an idempotency key the same as a transaction id?
Related but distinct: the client supplies the idempotency key to make a retry safe; the server’s transaction id identifies the resulting record.
Which requests need one?
Any state-changing, non-idempotent operation — payments, orders, transfers. Pure reads do not need one.
Keep reading
By Michael Gord · published 2026-10-09 · part of the Agentic Encyclopedia. Dates are the day of publication; events are cited at their own dates.