Agent Mesh
Go a2aa2a-protocolagent-meshagentic-aiinferencemcpmeshmesh-networknetwork-securitynetworking-aip2p-network
docs: /v1/* forwards the backend's Authorization header
Tomas Tormoca97809111cf
diff --git a/site/content/docs/concepts/networking.md b/site/content/docs/concepts/networking.mdindex 08462aec..fb3ba714 100644--- a/site/content/docs/concepts/networking.md+++ b/site/content/docs/concepts/networking.md@@ -26,9 +26,11 @@ is a good setup when everything that uses the node runs as the same user.The token travels in `X-Mesh-Authentication` and not in `Authorization`, sothat `Authorization` always means the same thing: the credential for theservice that is being called through the node. On the proxy path that header-is forwarded unchanged. The endpoints that never forward anything (`/mcp`,-`/v1/*`, `/mesh/service/*`) also accept the token in `Authorization`, for-clients that cannot set a custom header.+is forwarded unchanged. Every other route that needs the token also+accepts it in `Authorization`, for clients that cannot set a custom header.+The node removes the header that carried the token. On `/v1/*`, an+`Authorization` header that is still present is the backend's credential.+The node forwards it as on the proxy path.The API has four parts:diff --git a/site/content/docs/reference/node-api.md b/site/content/docs/reference/node-api.mdindex e9278b81..e348bcd1 100644--- a/site/content/docs/reference/node-api.md+++ b/site/content/docs/reference/node-api.md@@ -315,8 +315,9 @@ curl -s --unix-socket $SOCK http://localhost/v1/chat/completions \Any OpenAI SDK works with `base_url` set to `http://127.0.0.1:8080/v1` andthe API token, Task Biscuit, or platform JWT as `api_key`. The node accepts-the token in `Authorization` here because nothing on this path forwards that-header. Streaming responses are passed through. One provider can also be+the token in `Authorization` here and removes it. An `Authorization` header+that is not the token is the backend's credential, and the node forwards+it. Streaming responses are passed through. One provider can also beaddressed directly, at `/mesh/<peer-id>/inference/<name>/v1/chat/completions`.## Egress