RSS2JSON vs Wikipedia REST

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

Uptime · 30d
Uptime · 90d96.1%100%
Uptime · 30d96.7%100%
P50 · ms17898
P95 · ms1882961
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY-SA 4.0
Free tierFree — limits not publishedUnlimited within etiquette
Rate limitUnpublished200/sec global courtesy cap
In directory since2026-07-052026-05-09
operationalpartialdownno data

RSS2JSON vs Wikipedia REST: common questions

Which is more reliable, RSS2JSON or Wikipedia REST?

On our scheduled checks, Wikipedia REST leads on measured uptime — RSS2JSON at 96.1% versus Wikipedia REST at 100% 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, RSS2JSON or Wikipedia REST?

Wikipedia REST has the lower median latency in our checks — RSS2JSON responds in 178 ms versus Wikipedia REST at 98 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 RSS2JSON and Wikipedia REST need an API key?

Neither needs a paid key — RSS2JSON is callable with no signup, and Wikipedia REST is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call RSS2JSON and Wikipedia REST from the browser?

Yes — both RSS2JSON and Wikipedia REST send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are RSS2JSON and Wikipedia REST free for commercial use?

RSS2JSON has unclear commercial terms, and Wikipedia REST allows commercial use on its free tier. 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.