shipapis
StarSubmit an APISubmit API

GitHub REST API vs VATlayer

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

APIGitHub REST APIHEALTHY94VATlayerHEALTHY96
Uptime · 30d
Uptime · 90d99.44%100%
Uptime · 30d100%100%
P50 · ms349286
P95 · ms26712118
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GitHub REST API vs VATlayer: common questions

Which is more reliable, GitHub REST API or VATlayer?

On our scheduled checks, VATlayer leads on measured uptime — GitHub REST API at 99.44% versus VATlayer 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, GitHub REST API or VATlayer?

VATlayer has the lower median latency in our checks — GitHub REST API responds in 349 ms versus VATlayer at 286 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 VATlayer need an API key?

GitHub REST API needs no key, while VATlayer requires a free API key. If you want to start calling without signup, reach for GitHub REST API first.

Can I call GitHub REST API and VATlayer from the browser?

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

Are GitHub REST API and VATlayer free for commercial use?

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