国会会議録検索API vs GitHub Project Issues

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

Uptime · 30d
Uptime · 90d86.3%99.02%
Uptime · 30d100%98.3%
P50 · ms3456478
P95 · ms49904310
Authnonenone
CORSyesno
HTTPSyesyes
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

国会会議録検索API vs GitHub Project Issues: common questions

Which is more reliable, 国会会議録検索API or GitHub Project Issues?

On our scheduled checks, GitHub Project Issues leads on measured uptime — 国会会議録検索API at 86.3% versus GitHub Project Issues 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, 国会会議録検索API or GitHub Project Issues?

GitHub Project Issues has the lower median latency in our checks — 国会会議録検索API responds in 3456 ms versus GitHub Project Issues at 478 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 国会会議録検索API and GitHub Project Issues need an API key?

Neither needs a paid key — 国会会議録検索API is callable with no signup, and GitHub Project Issues is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call 国会会議録検索API and GitHub Project Issues from the browser?

Only 国会会議録検索API 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 国会会議録検索API and GitHub Project Issues free for commercial use?

国会会議録検索API has unclear commercial terms, and GitHub Project Issues 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.