Crates.io vs Spoo.me

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms458362
P95 · ms13171478
Authnonenone
CORSyesno
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

Crates.io vs Spoo.me: common questions

Which is more reliable, Crates.io or Spoo.me?

On our scheduled checks, Spoo.me leads on measured uptime — Crates.io at 99.02% versus Spoo.me at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Crates.io or Spoo.me?

Spoo.me has the lower median latency in our checks — Crates.io responds in 458 ms versus Spoo.me at 362 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Crates.io and Spoo.me need an API key?

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

Can I call Crates.io and Spoo.me from the browser?

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

Are Crates.io and Spoo.me free for commercial use?

Crates.io has unclear commercial terms, and Spoo.me 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.