Nekosia API vs Trace Moe

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree, no key; per-IP search quota applies
Rate limitUnpublishedConcurrency/quota limited per IP (check GET /me)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Nekosia API vs Trace Moe: common questions

Which is more reliable, Nekosia API or Trace Moe?

Only Trace Moe is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Nekosia API and Trace Moe need an API key?

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

Can I call Nekosia API and Trace Moe from the browser?

Yes — both Nekosia API and Trace Moe 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 Nekosia API and Trace Moe free for commercial use?

Nekosia API has unclear commercial terms, and Trace Moe 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.