shipapis
StarSubmit an APISubmit API

国会会議録検索API vs restful-api.dev

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

API国会会議録検索APINEW—restful-api.devNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
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 restful-api.dev: common questions

Which is more reliable, 国会会議録検索API or restful-api.dev?

On our scheduled checks, restful-api.dev leads on measured uptime — 国会会議録検索API at —% versus restful-api.dev 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 restful-api.dev need an API key?

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

Can I call 国会会議録検索API and restful-api.dev from the browser?

Only restful-api.dev 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 restful-api.dev free for commercial use?

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