GitHub Project Issues vs US Autocomplete

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms478683
P95 · ms43101917
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GitHub Project Issues vs US Autocomplete: common questions

Which is more reliable, GitHub Project Issues or US Autocomplete?

Both are neck-and-neck — GitHub Project Issues and US Autocomplete each measure 99.02% 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, GitHub Project Issues or US Autocomplete?

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

GitHub Project Issues needs no key, while US Autocomplete 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 US Autocomplete from the browser?

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

Are GitHub Project Issues and US Autocomplete free for commercial use?

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