shipapis
StarSubmit an APISubmit API

Replicate vs TensorFeed

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

APIReplicateDEAD0TensorFeedHEALTHY97
Uptime · 30d
Uptime · 90d0.0%100%
Uptime · 30d0.0%100%
P50 · ms—306
P95 · ms—752
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — no key (static JSON feed endpoints)
Rate limitUnpublished120 req/window · 119 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Replicate vs TensorFeed: common questions

Which is more reliable, Replicate or TensorFeed?

On our scheduled checks, TensorFeed leads on measured uptime — Replicate at 0.0% versus TensorFeed 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.

Do Replicate and TensorFeed need an API key?

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

Can I call Replicate and TensorFeed from the browser?

Only TensorFeed 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 TensorFeed free for commercial use?

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