shipapis
StarSubmit an APISubmit API

FakerAPI vs npm Registry

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

APIFakerAPIDEAD0npm RegistryHEALTHY98
Uptime · 30d
Uptime · 90d0.0%100%
Uptime · 30d0.0%100%
P50 · ms—201
P95 · ms—1246
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree (public registry)
Rate limit60 req/window · 59 remainingUnpublished (bulk scraping discouraged)
In directory since2026-07-052026-07-05
operationalpartialdownno data

FakerAPI vs npm Registry: common questions

Which is more reliable, FakerAPI or npm Registry?

On our scheduled checks, npm Registry leads on measured uptime — FakerAPI at 0.0% versus npm Registry 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.

Do FakerAPI and npm Registry need an API key?

Neither needs a paid key — FakerAPI is callable with no signup, and npm Registry is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call FakerAPI and npm Registry from the browser?

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

Are FakerAPI and npm Registry free for commercial use?

FakerAPI has unclear commercial terms, and npm Registry 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.