Their ESI router is generating the API specification at runtime from smaller route specifications, if one route is down then it won’t be able to combine them into the overall specification by the looks of it.
That is an absolutely terrible way to publish an API specification imo.
They need to publish their full specification from build time not runtime for app developers.
By having it published at runtime, we are also now unable to reliabily check it for development changes ourselves from a hash or diff.
Source: Introducing the ESI API - EVE: Developers
It’s not “magic”, it’s a “tombola”.
They even have a status API that doesn’t indicate that the routes are not combined into the spec.
A status API (meta get_status route) is the right way to show status is down, not by pulling it from a specification and they can’t even get that right.
I guess I won’t be building that client stub today whilst the API specification is “partial”.