shipapis
StarSubmit an APISubmit API

国会会議録検索API vs Fake JSON API

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

API国会会議録検索APIHEALTHY72Fake JSON APIHEALTHY88
Uptime · 30d
Uptime · 90d86.3%99.02%
Uptime · 30d100%98.3%
P50 · ms3456865
P95 · ms49902006
Authnonenone
CORSyesyes
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 Fake JSON API: common questions

Which is more reliable, 国会会議録検索API or Fake JSON API?

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

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

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

Can I call 国会会議録検索API and Fake JSON API from the browser?

Yes — both 国会会議録検索API and Fake JSON API send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are 国会会議録検索API and Fake JSON API free for commercial use?

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