Datamuse vs University of Oslo

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

Uptime · 30d
Uptime · 90d92.2%98.0%
Uptime · 30d86.7%100%
P50 · ms1801763
P95 · ms9264960
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Datamuse vs University of Oslo: common questions

Which is more reliable, Datamuse or University of Oslo?

On our scheduled checks, University of Oslo leads on measured uptime — Datamuse at 92.2% versus University of Oslo at 98.0% 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, Datamuse or University of Oslo?

Datamuse has the lower median latency in our checks — Datamuse responds in 180 ms versus University of Oslo at 1763 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 Datamuse and University of Oslo need an API key?

Neither needs a paid key — Datamuse is callable with no signup, and University of Oslo is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Datamuse and University of Oslo from the browser?

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

Are Datamuse and University of Oslo free for commercial use?

Datamuse has unclear commercial terms, and University of Oslo 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.