Skip to content

Agent Mesh

docs: fix the link to the node's token endpoint section

Tomas Tormod9ea94d21f4d
diff --git a/site/content/docs/reference/node-api.md b/site/content/docs/reference/node-api.md
index 16c3c839..b298d738 100644
--- a/site/content/docs/reference/node-api.md
+++ b/site/content/docs/reference/node-api.md
@@ -49,7 +49,7 @@ Authorization Server.
| `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). |
+| `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-and-revocation-oauthrevoke). |
| `POST /oauth/revoke` | token, or none when the Biscuit verifies | RFC 7009 Token Revocation: revokes a task Biscuit in this node's local revocation cache. |
| `GET /metrics` | token | Prometheus metrics (`agentmesh_node_*`). |
| `POST /mcp` | token | The MCP server (Streamable HTTP, sessionless: no `Mcp-Session-Id`, `GET` answers `405`). |