FinSignals API vs TimeAPI.io

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms3121040
P95 · ms14193967
Authnonenone
CORSyesyes
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

FinSignals API vs TimeAPI.io: common questions

Which is more reliable, FinSignals API or TimeAPI.io?

Both are neck-and-neck — FinSignals API and TimeAPI.io 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, FinSignals API or TimeAPI.io?

FinSignals API has the lower median latency in our checks — FinSignals API responds in 312 ms versus TimeAPI.io at 1040 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 FinSignals API and TimeAPI.io need an API key?

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

Can I call FinSignals API and TimeAPI.io from the browser?

Yes — both FinSignals API and TimeAPI.io 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 FinSignals API and TimeAPI.io free for commercial use?

FinSignals API has unclear commercial terms, and TimeAPI.io 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.