Edgrapi vs Sugra

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

Uptime · 30d
Uptime · 90d95.6%97.8%
Uptime · 30d100%96.7%
P50 · ms279452
P95 · ms39654052
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Edgrapi vs Sugra: common questions

Which is more reliable, Edgrapi or Sugra?

On our scheduled checks, Sugra leads on measured uptime — Edgrapi at 95.6% versus Sugra at 97.8% 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, Edgrapi or Sugra?

Edgrapi has the lower median latency in our checks — Edgrapi responds in 279 ms versus Sugra at 452 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 Edgrapi and Sugra need an API key?

Both ask you to authenticate — Edgrapi uses an API key and Sugra uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Edgrapi and Sugra from the browser?

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

Are Edgrapi and Sugra free for commercial use?

Edgrapi has unclear commercial terms, and Sugra 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.