OnSched Consumer API vs ReportForge

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms7221362
P95 · ms18902016
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OnSched Consumer API vs ReportForge: common questions

Which is more reliable, OnSched Consumer API or ReportForge?

Both are neck-and-neck — OnSched Consumer API and ReportForge 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, OnSched Consumer API or ReportForge?

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

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

Can I call OnSched Consumer API and ReportForge from the browser?

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

Are OnSched Consumer API and ReportForge free for commercial use?

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