RSS2JSON vs SnapshotAPI

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

Uptime · 30d
Uptime · 90d96.1%6.9%
Uptime · 30d96.7%0.0%
P50 · ms178396
P95 · ms1882547
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

RSS2JSON vs SnapshotAPI: common questions

Which is more reliable, RSS2JSON or SnapshotAPI?

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

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

RSS2JSON needs no key, while SnapshotAPI requires a free API key. If you want to start calling without signup, reach for RSS2JSON first.

Can I call RSS2JSON and SnapshotAPI from the browser?

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

Are RSS2JSON and SnapshotAPI free for commercial use?

RSS2JSON has unclear commercial terms, and SnapshotAPI 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.