ThronesApi vs Verome

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

Uptime · 30d
Uptime · 90d97.1%38.2%
Uptime · 30d95.0%0.0%
P50 · ms890884
P95 · ms45934329
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

ThronesApi vs Verome: common questions

Which is more reliable, ThronesApi or Verome?

On our scheduled checks, ThronesApi leads on measured uptime — ThronesApi at 97.1% versus Verome at 38.2% 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, ThronesApi or Verome?

Verome has the lower median latency in our checks — ThronesApi responds in 890 ms versus Verome at 884 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 ThronesApi and Verome need an API key?

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

Can I call ThronesApi and Verome from the browser?

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

Are ThronesApi and Verome free for commercial use?

ThronesApi has unclear commercial terms, and Verome 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.