Edgrapi vs Markbase

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

Uptime · 30d
Uptime · 90d95.6%98.3%
Uptime · 30d100%96.7%
P50 · ms279581
P95 · ms39651492
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublished30 req/window · 29 remaining · resets 1783519324
In directory since2026-07-052026-07-05
operationalpartialdownno data

Edgrapi vs Markbase: common questions

Which is more reliable, Edgrapi or Markbase?

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

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

Markbase needs no key, while Edgrapi requires a free API key. If you want to start calling without signup, reach for Markbase first.

Can I call Edgrapi and Markbase from the browser?

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

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