Municipal Finance API vs ValueRay

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

Uptime · 30d
Uptime · 90d96.1%100%
Uptime · 30d98.3%100%
P50 · ms2094553
P95 · ms29521106
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished50 req/window · 49 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Municipal Finance API vs ValueRay: common questions

Which is more reliable, Municipal Finance API or ValueRay?

On our scheduled checks, ValueRay leads on measured uptime — Municipal Finance API at 96.1% versus ValueRay 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, Municipal Finance API or ValueRay?

ValueRay has the lower median latency in our checks — Municipal Finance API responds in 2094 ms versus ValueRay at 553 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 Municipal Finance API and ValueRay need an API key?

Neither needs a paid key — Municipal Finance API is callable with no signup, and ValueRay is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Municipal Finance API and ValueRay from the browser?

Yes — both Municipal Finance API and ValueRay 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 Municipal Finance API and ValueRay free for commercial use?

Municipal Finance API has unclear commercial terms, and ValueRay 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.