PredictHQ vs Urlbox API

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
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

PredictHQ vs Urlbox API: common questions

Which is more reliable, PredictHQ or Urlbox API?

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

Both ask you to authenticate — PredictHQ uses an API key and Urlbox API 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 PredictHQ and Urlbox API from the browser?

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

Are PredictHQ and Urlbox API free for commercial use?

PredictHQ has unclear commercial terms, and Urlbox 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.