shipapis
StarSubmit an APISubmit API

Edgrapi vs Markbase

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

APIEdgrapiHEALTHY79MarkbaseHEALTHY85
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%98.3%
P50 · ms1662866
P95 · ms39971568
AuthapiKeynone
CORSnoyes
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?

Both are neck-and-neck — Edgrapi and Markbase each measure 99.02% 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, Edgrapi or Markbase?

Markbase has the lower median latency in our checks — Edgrapi responds in 1662 ms versus Markbase at 866 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?

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

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.