Service status
Whether the API is serving, what it depends on to serve, and which
contract version it is currently on. Reaching it at all proves the
process is up and routing; status and dependencies say whether it is
up in a useful sense.
Every check is shallow. It proves that a dependency answers, not that it
answers correctly, so read a down as a reason to stop retrying and
never an up as a guarantee that a write elsewhere will land.
The answer is coarse: capability names and states, no vendor and no free text, and no distinction between a dependency that failed its probe and one Commune cannot reach at all.
The one operation that takes no credential, and the one that ignores
Commune-Version. With no key to count against, the per-key budgets do
not apply and no RateLimit-* headers are returned. Whatever sits in
front of this service can still refuse a request, which is why 429
stays declared.
Loading...
Waiting for a request to be sent.