shipapis
StarSubmit an APISubmit API

Replicate vs SHARE

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

APIReplicateNEW—SHARENEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
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 SHARE: common questions

Which is more reliable, Replicate or SHARE?

On our scheduled checks, SHARE leads on measured uptime — Replicate at —% versus SHARE 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 SHARE need an API key?

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

Can I call Replicate and SHARE from the browser?

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

Are Replicate and SHARE free for commercial use?

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