Magic 8-Ball API vs Public Time API

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms442242
P95 · ms1134382
Authnonenone
CORSnono
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

Magic 8-Ball API vs Public Time API: common questions

Which is more reliable, Magic 8-Ball API or Public Time API?

Both are neck-and-neck — Magic 8-Ball API and Public Time API each measure 100% 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.

Which is faster, Magic 8-Ball API or Public Time API?

Public Time API has the lower median latency in our checks — Magic 8-Ball API responds in 442 ms versus Public Time API at 242 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 Magic 8-Ball API and Public Time API need an API key?

Neither needs a paid key — Magic 8-Ball API is callable with no signup, and Public Time API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Magic 8-Ball API and Public Time API from the browser?

Neither sends browser-friendly CORS headers reliably, so call Magic 8-Ball API and Public Time API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Magic 8-Ball API and Public Time API free for commercial use?

Magic 8-Ball API has unclear commercial terms, and Public Time 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.