shipapis
StarSubmit an APISubmit API

GitHub Project Issues vs Hunter

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

APIGitHub Project IssuesHEALTHY90HunterHEALTHY96
Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms478362
P95 · ms4310859
AuthnoneapiKey
CORSnono
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 Project Issues vs Hunter: common questions

Which is more reliable, GitHub Project Issues or Hunter?

On our scheduled checks, Hunter leads on measured uptime — GitHub Project Issues at 99.02% versus Hunter 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 Project Issues or Hunter?

Hunter has the lower median latency in our checks — GitHub Project Issues responds in 478 ms versus Hunter at 362 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 Project Issues and Hunter need an API key?

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

Can I call GitHub Project Issues and Hunter from the browser?

Neither sends browser-friendly CORS headers reliably, so call GitHub Project Issues and Hunter from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are GitHub Project Issues and Hunter free for commercial use?

GitHub Project Issues has unclear commercial terms, and Hunter 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.