Ntropy Transaction API v1 vs Telegraph

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

Uptime · 30d
Uptime · 90d98.0%99.02%
Uptime · 30d96.7%100%
P50 · ms1223801
P95 · ms44843497
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Ntropy Transaction API v1 vs Telegraph: common questions

Which is more reliable, Ntropy Transaction API v1 or Telegraph?

On our scheduled checks, Telegraph leads on measured uptime — Ntropy Transaction API v1 at 98.0% versus Telegraph at 99.02% 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, Ntropy Transaction API v1 or Telegraph?

Telegraph has the lower median latency in our checks — Ntropy Transaction API v1 responds in 1223 ms versus Telegraph at 801 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 Ntropy Transaction API v1 and Telegraph need an API key?

Ntropy Transaction API v1 needs no key, while Telegraph requires a free API key. If you want to start calling without signup, reach for Ntropy Transaction API v1 first.

Can I call Ntropy Transaction API v1 and Telegraph from the browser?

Only Telegraph is browser-friendly — it returns CORS headers over HTTPS. Ntropy Transaction API v1 needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Ntropy Transaction API v1 and Telegraph free for commercial use?

Ntropy Transaction API v1 has unclear commercial terms, and Telegraph 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.