shipapis
StarSubmit an APISubmit API

USPTO vs TensorFeed

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

APIUSPTONEW—TensorFeedNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
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

USPTO vs TensorFeed: common questions

Which is more reliable, USPTO or TensorFeed?

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

Neither needs a paid key — USPTO 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 USPTO and TensorFeed from the browser?

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

Are USPTO and TensorFeed free for commercial use?

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