shipapis
StarSubmit an APISubmit API

SHARE vs USPTO

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

APISHAREHEALTHY96USPTOHEALTHY80
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms3531141
P95 · ms7593848
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

SHARE vs USPTO: common questions

Which is more reliable, SHARE or USPTO?

Both are neck-and-neck — SHARE and USPTO each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, SHARE or USPTO?

SHARE has the lower median latency in our checks — SHARE responds in 353 ms versus USPTO at 1141 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do SHARE and USPTO need an API key?

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

Can I call SHARE and USPTO from the browser?

Only SHARE 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 SHARE and USPTO free for commercial use?

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