Markbase vs Unirate

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms866324
P95 · ms1568611
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limit30 req/window · 29 remaining · resets 1783519324Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Markbase vs Unirate: common questions

Which is more reliable, Markbase or Unirate?

On our scheduled checks, Unirate leads on measured uptime — Markbase at 99.02% versus Unirate 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, Markbase or Unirate?

Unirate has the lower median latency in our checks — Markbase responds in 866 ms versus Unirate at 324 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 Markbase and Unirate need an API key?

Markbase needs no key, while Unirate requires a free API key. If you want to start calling without signup, reach for Markbase first.

Can I call Markbase and Unirate from the browser?

Yes — both Markbase and Unirate send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Markbase and Unirate free for commercial use?

Markbase has unclear commercial terms, and Unirate 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.