FBI Wanted vs LocalGov.jp

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

Uptime · 30d
Uptime · 90d94.1%100%
Uptime · 30d98.3%100%
P50 · ms3781274
P95 · ms25821718
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0 (attribution: "via LocalGov.jp")
Free tierFree — limits not publishedFree — all endpoints currently free (per llms.txt)
Rate limitRetry-After: 47245s30 req/window · 29 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

FBI Wanted vs LocalGov.jp: common questions

Which is more reliable, FBI Wanted or LocalGov.jp?

On our scheduled checks, LocalGov.jp leads on measured uptime — FBI Wanted at 94.1% versus LocalGov.jp at 100% 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, FBI Wanted or LocalGov.jp?

FBI Wanted has the lower median latency in our checks — FBI Wanted responds in 378 ms versus LocalGov.jp at 1274 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 FBI Wanted and LocalGov.jp need an API key?

Neither needs a paid key — FBI Wanted is callable with no signup, and LocalGov.jp is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call FBI Wanted and LocalGov.jp from the browser?

Yes — both FBI Wanted and LocalGov.jp 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 FBI Wanted and LocalGov.jp free for commercial use?

FBI Wanted has unclear commercial terms, and LocalGov.jp 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.