国会会議録検索API vs ipify

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedn/a
Free tierFree — limits not publishedUnlimited
Rate limitUnpublishedNone
In directory since2026-07-052026-05-02
operationalpartialdownno data

国会会議録検索API vs ipify: common questions

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

On our scheduled checks, ipify leads on measured uptime — 国会会議録検索API at —% versus ipify at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do 国会会議録検索API and ipify need an API key?

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

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

Only ipify is browser-friendly — it returns CORS headers over HTTPS. 国会会議録検索API needs a server-side call or proxy, so factor that into which one fits a front-end project.

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

国会会議録検索API has unclear commercial terms, and ipify allows commercial use on its free tier. 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.