shipapis
StarSubmit an APISubmit API

F1 API vs Lexigram

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

APIF1 APIHEALTHY47LexigramHEALTHY88
Uptime · 30d
Uptime · 90d45.1%99.02%
Uptime · 30d50.0%98.3%
P50 · ms4909807
P95 · ms49991672
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

F1 API vs Lexigram: common questions

Which is more reliable, F1 API or Lexigram?

On our scheduled checks, Lexigram leads on measured uptime — F1 API at 45.1% versus Lexigram at 99.02% 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, F1 API or Lexigram?

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

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

Can I call F1 API and Lexigram from the browser?

Only F1 API 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 F1 API and Lexigram free for commercial use?

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