Replicate vs USPTO

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Replicate vs USPTO: common questions

Which is more reliable, Replicate or USPTO?

On our scheduled checks, USPTO leads on measured uptime — Replicate at —% versus USPTO at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Replicate and USPTO need an API key?

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

Can I call Replicate and USPTO from the browser?

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

Are Replicate and USPTO free for commercial use?

Replicate has unclear commercial terms, and USPTO 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.