Edgrapi vs Twelve Data

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%98.3%
P50 · ms1662253
P95 · ms39974851
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Edgrapi vs Twelve Data: common questions

Which is more reliable, Edgrapi or Twelve Data?

Both are neck-and-neck — Edgrapi and Twelve Data 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 Twelve Data?

Twelve Data has the lower median latency in our checks — Edgrapi responds in 1662 ms versus Twelve Data at 253 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 Twelve Data need an API key?

Both ask you to authenticate — Edgrapi uses an API key and Twelve Data 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 Twelve Data from the browser?

Only Twelve Data 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 Twelve Data free for commercial use?

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