shipapis
StarSubmit an APISubmit API

ParlayAPI vs RSQ API

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

APIParlayAPIREACHABLE88RSQ APIHEALTHY93
Uptime · 30d
Uptime · 90d87.5%100%
Uptime · 30d87.5%100%
P50 · ms211172
P95 · ms15364248
AuthapiKeynone
CORSnoyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-10-042026-07-05
operationalpartialdownno data

ParlayAPI vs RSQ API: common questions

Which is more reliable, ParlayAPI or RSQ API?

On our scheduled checks, RSQ API leads on measured uptime — ParlayAPI at 87.5% versus RSQ API 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, ParlayAPI or RSQ API?

RSQ API has the lower median latency in our checks — ParlayAPI responds in 211 ms versus RSQ API at 172 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 ParlayAPI and RSQ API need an API key?

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

Can I call ParlayAPI and RSQ API from the browser?

Neither sends browser-friendly CORS headers reliably, so call ParlayAPI and RSQ API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are ParlayAPI and RSQ API free for commercial use?

ParlayAPI has unclear commercial terms, and RSQ API 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.