Shields vs Web of Science API Expanded

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Shields vs Web of Science API Expanded: common questions

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

On our scheduled checks, Web of Science API Expanded leads on measured uptime — Shields at —% versus Web of Science API Expanded at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Shields and Web of Science API Expanded need an API key?

Shields needs no key, while Web of Science API Expanded requires a free API key. If you want to start calling without signup, reach for Shields first.

Can I call Shields and Web of Science API Expanded from the browser?

Only Shields 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 Shields and Web of Science API Expanded free for commercial use?

Shields 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.