shipapis
StarSubmit an APISubmit API

Lexigram vs Padel Snipe

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

APILexigramHEALTHY88Padel SnipeHEALTHY69
Uptime · 30d
Uptime · 90d99.02%82.4%
Uptime · 30d98.3%80.0%
P50 · ms8073830
P95 · ms16724941
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC-BY 4.0
Free tierFree tier — key may be requiredFree — no auth
Rate limitUnpublishedFair use — no hard limit stated
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lexigram vs Padel Snipe: common questions

Which is more reliable, Lexigram or Padel Snipe?

On our scheduled checks, Lexigram leads on measured uptime — Lexigram at 99.02% versus Padel Snipe at 82.4% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Lexigram or Padel Snipe?

Lexigram has the lower median latency in our checks — Lexigram responds in 807 ms versus Padel Snipe at 3830 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 Lexigram and Padel Snipe need an API key?

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

Can I call Lexigram and Padel Snipe from the browser?

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

Lexigram has unclear commercial terms, and Padel Snipe allows commercial use on its free tier. 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.