Idempotency: protecting against retries
Idempotency protects against the same request being processed twice because the client retried it — the client knows it's making the same request again, and the key tells the server to recognize that.
Deduplication: catching independent duplicates
Deduplication catches a different case: two genuinely separate requests or enrollments that turn out to represent the same underlying thing — for instance, two different enrollment attempts that both belong to the same real person.
Why an identity system needs both
Idempotency alone won't catch someone enrolling twice through two unrelated sessions. Deduplication — checking a new enrollment against existing embeddings before accepting it — is what catches that case, and the two mechanisms aren't substitutes for each other.