idempotency in api post requests, necessary evil or best practice

i've been thinking about idempotency for POST requests lately, specifically for operations that create resources. it's straightforward for PUT or DELETE, but for POST, how are you all handling ensuring a client doesn't accidentally create duplicates if they retry a request? are you using unique client-generated IDs? relying on server-side checks? what are the trade-offs you've encountered