Skip to content

Agent Mesh

docs: name the node routes that answer 503 while disconnected

Tomas Tormo57d3b3e0a0c1
diff --git a/site/content/docs/reference/node-api.md b/site/content/docs/reference/node-api.md
index 48474f25..26230634 100644
--- a/site/content/docs/reference/node-api.md
+++ b/site/content/docs/reference/node-api.md
@@ -46,7 +46,7 @@ Authorization Server.
| Route | Auth | Purpose |
|---|---|---|
| `GET /healthz` | none | `200` while the process is up. |
-| `GET /readyz` | none | `200` once the node is connected to the mesh, that is, holds an authenticated connection to a router, and `503` until then. Every other route except `/debug/*` and `/.well-known/*` answers `503` until the node is connected to the mesh. |
+| `GET /readyz` | none | `200` once the node is connected to the mesh, that is, holds an authenticated connection to a router. Until then `/readyz`, `/mcp`, `/v1/*`, `/mesh/service/discover`, `/mesh/{peer-id}/...` and `/mesh/peer/*` answer `503`. Every other route answers while the node is disconnected. |
| `GET /.well-known/oauth-protected-resource` | none | RFC 9728 OAuth 2.1 Protected Resource Metadata naming the Agent Mesh control plane in `authorization_servers`. |
| `GET /.well-known/oauth-authorization-server` | none | RFC 8414 metadata for this node's token endpoint: the grant types and client authentication methods it accepts. |
| `POST /oauth/token` | token or client assertion | Token endpoint: RFC 8693 token exchange, RFC 7523 client assertion and JWT authorization grants. Every grant returns a Delegated or Task-Attenuated Biscuit. See [Token endpoint (`/oauth/token`)](#token-endpoint-oauthtoken). |