MY IP vs OnSched Consumer API

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

Uptime · 30d
Uptime · 90d82.4%100%
Uptime · 30d70.0%100%
P50 · ms210722
P95 · ms11451890
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitRetry-After: 721sUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

MY IP vs OnSched Consumer API: common questions

Which is more reliable, MY IP or OnSched Consumer API?

On our scheduled checks, OnSched Consumer API leads on measured uptime — MY IP at 82.4% versus OnSched Consumer API 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, MY IP or OnSched Consumer API?

MY IP has the lower median latency in our checks — MY IP responds in 210 ms versus OnSched Consumer API at 722 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 MY IP and OnSched Consumer API need an API key?

MY IP needs no key, while OnSched Consumer API requires a free API key. If you want to start calling without signup, reach for MY IP first.

Can I call MY IP and OnSched Consumer API from the browser?

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

Are MY IP and OnSched Consumer API free for commercial use?

MY IP has unclear commercial terms, and OnSched Consumer 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.