shipapis
StarSubmit an APISubmit API

Lexigram vs SharpAPI

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

APILexigramNEW—SharpAPINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lexigram vs SharpAPI: common questions

Which is more reliable, Lexigram or SharpAPI?

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

Both ask you to authenticate — Lexigram uses an API key and SharpAPI uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Lexigram and SharpAPI from the browser?

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

Are Lexigram and SharpAPI free for commercial use?

Lexigram has unclear commercial terms, and SharpAPI 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.