F1 API vs ICD-10 Codes

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

Uptime · 30d
Uptime · 90d45.1%100%
Uptime · 30d50.0%100%
P50 · ms49091831
P95 · ms49993898
Authnonenone
CORSyesyes
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

F1 API vs ICD-10 Codes: common questions

Which is more reliable, F1 API or ICD-10 Codes?

On our scheduled checks, ICD-10 Codes leads on measured uptime — F1 API at 45.1% versus ICD-10 Codes at 100% 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 ICD-10 Codes?

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

Neither needs a paid key — F1 API is callable with no signup, and ICD-10 Codes is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call F1 API and ICD-10 Codes from the browser?

Yes — both F1 API and ICD-10 Codes send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are F1 API and ICD-10 Codes free for commercial use?

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