shipapis
StarSubmit an APISubmit API

Disify vs xfetch

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

APIDisifyDYING38xfetchDEAD0
Uptime · 30d
Uptime · 90d42.2%0.0%
Uptime · 30d28.3%0.0%
P50 · ms1075—
P95 · ms1679—
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limit30 req/window · 21 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Disify vs xfetch: common questions

Which is more reliable, Disify or xfetch?

On our scheduled checks, Disify leads on measured uptime — Disify at 42.2% versus xfetch at 0.0% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Disify and xfetch need an API key?

Disify needs no key, while xfetch requires a free API key. If you want to start calling without signup, reach for Disify first.

Can I call Disify and xfetch from the browser?

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

Are Disify and xfetch free for commercial use?

Disify 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.