Attack on Titan API vs Trace Moe

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms501708
P95 · ms17931179
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

Attack on Titan API vs Trace Moe: common questions

Which is more reliable, Attack on Titan API or Trace Moe?

Both are neck-and-neck — Attack on Titan API and Trace Moe each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Attack on Titan API or Trace Moe?

Attack on Titan API has the lower median latency in our checks — Attack on Titan API responds in 501 ms versus Trace Moe at 708 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 Attack on Titan API and Trace Moe need an API key?

Neither needs a paid key — Attack on Titan 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 Attack on Titan API and Trace Moe from the browser?

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

Attack on Titan 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.