Invokely vs Web of Science API Expanded

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

Uptime · 30d
Uptime · 90d100%99.44%
Uptime · 30d100%100%
P50 · ms227649
P95 · ms2451985
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree tier — API key required
Rate limitUnpublished
In directory since2026-10-122026-07-05
operationalpartialdownno data

Invokely vs Web of Science API Expanded: common questions

Which is more reliable, Invokely or Web of Science API Expanded?

On our scheduled checks, Invokely leads on measured uptime — Invokely at 100% versus Web of Science API Expanded at 99.44% 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, Invokely or Web of Science API Expanded?

Invokely has the lower median latency in our checks — Invokely responds in 227 ms versus Web of Science API Expanded at 649 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 Invokely and Web of Science API Expanded need an API key?

Both ask you to authenticate — Invokely uses an API key and Web of Science API Expanded 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 Invokely and Web of Science API Expanded from the browser?

Only Invokely is browser-friendly — it returns CORS headers over HTTPS. Web of Science API Expanded needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Invokely and Web of Science API Expanded free for commercial use?

Invokely has unclear commercial terms, and Web of Science API Expanded 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.