ImprovMX API vs xfetch

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

Uptime · 30d
Uptime · 90d0.0%0.0%
Uptime · 30d0.0%0.0%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limit301 req/window · 300 remaining · resets 1783526520Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ImprovMX API vs xfetch: common questions

Which is more reliable, ImprovMX API or xfetch?

Both are neck-and-neck — ImprovMX API 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 ImprovMX API and xfetch need an API key?

Both ask you to authenticate — ImprovMX API 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 ImprovMX API and xfetch from the browser?

Yes — both ImprovMX API and xfetch send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are ImprovMX API and xfetch free for commercial use?

ImprovMX API 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.