shipapis
StarSubmit an APISubmit API

Render API vs ScreenURL

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

APIRender APIDEAD0ScreenURLDEAD0
Uptime · 30d
Uptime · 90d0.0%0.0%
Uptime · 30d0.0%0.0%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Render API vs ScreenURL: common questions

Which is more reliable, Render API or ScreenURL?

Both are neck-and-neck — Render API and ScreenURL each measure 0.0% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Do Render API and ScreenURL need an API key?

Both ask you to authenticate — Render API uses an API key and ScreenURL uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Render API and ScreenURL from the browser?

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

Are Render API and ScreenURL free for commercial use?

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