GitHub REST API vs What The Commit

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms5681312
P95 · ms26714279
Authnonenone
CORSyesyes
HTTPSyesno
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

GitHub REST API vs What The Commit: common questions

Which is more reliable, GitHub REST API or What The Commit?

On our scheduled checks, GitHub REST API leads on measured uptime — GitHub REST API at 100% versus What The Commit at 99.02% 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, GitHub REST API or What The Commit?

GitHub REST API has the lower median latency in our checks — GitHub REST API responds in 568 ms versus What The Commit at 1312 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 GitHub REST API and What The Commit need an API key?

Neither needs a paid key — GitHub REST API is callable with no signup, and What The Commit is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call GitHub REST API and What The Commit from the browser?

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

Are GitHub REST API and What The Commit free for commercial use?

GitHub REST API has unclear commercial terms, and What The Commit 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.