The request asks what to use for API idempotency and retry, and none of the candidate sources describes an idempotency or retry mechanism directly. The closest fit is Supabase 2, whose action record notes that its create_task action should not be retried blindly after a connection failure 12, and whose upsert_row action inserts or updates a row 12, which can make a retried write safe to repeat. Resend 3 and Plaid 7 show relevant retry-related endpoints, but their pages do not describe
A question back: Which API or platform are you calling (for example, a specific payments, email or database service), so I can recommend the idempotency and retry approach its documentation supports?
- 1
Supabasesupabase.comverified and signed
Its upsert_row action inserts or updates a row, which can make a repeated write idempotent 12, and its create_task action warns against blind retries after a connection failure 12.
official:SDK · @supabase/supabase-jsCLI · supabasepackage · Supabaserepository · supabaseskill · supabase-postgres-best-practices+103 community tools built for it
for agents: custom_api_call · create_task · upsert_row
- 2
Resendresend.comverified and signed
Its API exposes create and delete endpoints for API keys 13, but the source does not describe idempotency keys or retry handling.
+12 community tools built for it
for agents: DELETE /api-keys/{api_key_id} · DELETE /api-keys/{api_key_id} · POST /api-keys
- 3
Plaid APIplaid.comverified and signed
Its identityVerificationRetry action retries an identity verification 17, but the source does not describe idempotency keys or general retry handling.
official:API · The Plaid API+16 community tools built for it
for agents: identityVerificationRetry · webhookVerificationKeyGet · transactionsEnhance
Sources
- 2Supabase | The Postgres Development Platformsupabase.com · read 2026-10-29
- 3Resend · Email for developersresend.com · read 2026-10-29
- 7Home | Plaid Docsplaid.com · read 2026-10-29
- 12Supabase (Activepieces): declares "custom_api_call" (the record we read and signed)unfragile.ai · read 2026-10-24
- 13Resend: declares "DELETE /api-keys/{api_key_id}" (the record we read and signed)unfragile.ai · read 2026-10-24
- 17The Plaid API: declares "identityVerificationRetry" (the record we read and signed)unfragile.ai · read 2026-10-24
For agents: the 10 actions behind this answer
custom_api_call · GitHub (Activepieces) verified and signed
Custom API Call — Make a custom API call to a specific endpoint
custom_api_call · Supabase (Activepieces) verified and signed
Custom API Call — Make a custom API call to a specific endpoint
DELETE /api-keys/{api_key_id} · Resend verified and signed
Remove an existing API key
· aio-libs Aiobotocore website read, tools not yet checked
clerk-backend-api · clerk-backend-api verified and signed
Clerk Backend REST API explorer and executor. Browse tags, inspect endpoint schemas, and execute authenticated requests. Use when listing users, managing organizations, or calling any Clerk API endpoint.
· aio-libs Aiohttp website read, tools not yet checked
middleware · nemo-relay verified and signed
identityVerificationRetry · The Plaid API verified and signed
Retry an Identity Verification
· async-std website read, tools not yet checked
A Rust library for easy and understandable async programming
· hyper website read, tools not yet checked
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.