IBANforge vs ValueRay

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms694553
P95 · ms22461106
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tier200 requests/month with a free API key; /v1/demo and /health are keylessFree — limits not published
Rate limitUnpublished (200/month free quota)50 req/window · 49 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

IBANforge vs ValueRay: common questions

Which is more reliable, IBANforge or ValueRay?

Both are neck-and-neck — IBANforge and ValueRay each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, IBANforge or ValueRay?

ValueRay has the lower median latency in our checks — IBANforge responds in 694 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 IBANforge and ValueRay need an API key?

Neither needs a paid key — IBANforge 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 IBANforge and ValueRay from the browser?

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

IBANforge 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.