shipapis
StarSubmit an APISubmit API

Resend vs xfetch

Same instrument, two spec sheets — measured, not claimed.

APIResendDEAD0xfetchDEAD0
Uptime · 30d
Uptime · 90d0.0%0.0%
Uptime · 30d0.0%0.0%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Resend vs xfetch: common questions

Which is more reliable, Resend or xfetch?

Both are neck-and-neck — Resend and xfetch each measure 0.0% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Do Resend and xfetch need an API key?

Both ask you to authenticate — Resend uses an API key and xfetch uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Resend and xfetch from the browser?

Only xfetch is browser-friendly — it returns CORS headers over HTTPS. Resend needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Resend and xfetch free for commercial use?

Resend has unclear commercial terms, and xfetch has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.