shipapis
StarSubmit an APISubmit API

SHARE vs TensorFeed

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

APISHARENEW—TensorFeedNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key (static JSON feed endpoints)
Rate limitUnpublished120 req/window · 119 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

SHARE vs TensorFeed: common questions

Which is more reliable, SHARE or TensorFeed?

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

Neither needs a paid key — SHARE is callable with no signup, and TensorFeed is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call SHARE and TensorFeed from the browser?

Yes — both SHARE and TensorFeed send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are SHARE and TensorFeed free for commercial use?

SHARE 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.