ModelPartFinder Error Codes vs Registrum API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ModelPartFinder Error Codes vs Registrum API: common questions

Which is more reliable, ModelPartFinder Error Codes or Registrum API?

On our scheduled checks, Registrum API leads on measured uptime — ModelPartFinder Error Codes at —% versus Registrum API 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 ModelPartFinder Error Codes and Registrum API need an API key?

ModelPartFinder Error Codes needs no key, while Registrum API requires a free API key. If you want to start calling without signup, reach for ModelPartFinder Error Codes first.

Can I call ModelPartFinder Error Codes and Registrum API from the browser?

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

Are ModelPartFinder Error Codes and Registrum API free for commercial use?

ModelPartFinder Error Codes has unclear commercial terms, and Registrum API 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.