Catchdoms Security API vs Crates.io

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Catchdoms Security API vs Crates.io: common questions

Which is more reliable, Catchdoms Security API or Crates.io?

On our scheduled checks, Crates.io leads on measured uptime — Catchdoms Security API at —% versus Crates.io at —% 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 Catchdoms Security API and Crates.io need an API key?

Neither needs a paid key — Catchdoms Security API is callable with no signup, and Crates.io is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Catchdoms Security API and Crates.io from the browser?

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

Are Catchdoms Security API and Crates.io free for commercial use?

Catchdoms Security API has unclear commercial terms, and Crates.io 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.