a2be755b7d
Delegating Agent Network today means handing out full account admin, and regular users cannot see their own usage or how to connect a local tool. Add two roles on top of the existing agent_network permission submodules. agent_network_admin owns the whole area (providers, policies, guardrails, budgets, usage, logs, settings) with read-only users, groups, peers, and account info needed to build policies, and nothing else in the account. usage_viewer is the regular User baseline plus read on the aggregated usage and cost overview: no provider configuration, no policies, no request-level logs, which can contain captured prompts. billing_admin gets a proper permission-map entry with the User baseline so role resolution stops failing with role-not-found; its plan and invoice permissions stay enforced cloud-side. Add the self-service endpoints behind the "My Agent Network" view, available to every authenticated user because both answers are scoped strictly to the caller. GET /api/agent-network/me/setup returns the account endpoint plus the providers and models the caller's own groups authorize, computed with the same rules the proxy enforces: policy filtering as in policy selection, model allowlist union intersected with declared models, orphan and disabled providers omitted. Not set up and no access are deliberately indistinguishable, and the response carries display metadata only. GET /api/agent-network/me/consumption returns the caller's own user-dimension counters. Linear: NET-1399
NetBird Agent Network
Agent Network is NetBird's access control layer for AI agents and the people who run them. It gives every agent a real identity, tied to an identity provider (IdP), and governs what it can reach: LLM APIs and AI gateways it can call, and the internal resources it can access. Traffic flows only over the encrypted NetBird tunnel, scoped by policy, with no API keys or other credentials to leak. It also gives you control over cost and token usage.
Because every LLM request passes through an identity-aware proxy, you can:
- Set spending and rate limits per agent, per user, or per team — with hard caps that stop requests once a budget is reached.
- Restrict models and providers so agents can only call approved (and cost-appropriate) endpoints, keeping expensive models off-limits unless explicitly allowed.
- Attribute usage by tracking token consumption and cost per identity, group, or cost center so every request is tied back to the agent and person responsible.
- Reuse your existing AI gateway — point the proxy at a gateway you already run, keeping its routing and config in place while it adds identity on top, so you skip API key distribution.
https://github.com/user-attachments/assets/44d18286-d8ab-49f8-a457-98ccd66f3268
Beta. Agent Network is in beta, but it's stable and already running in production environments. It's fully open source and can be self-hosted on your own infrastructure, with no vendor lock-in and no data leaving your environment.
How it works
Say you have a simple use case: your Engineering or IT team needs access to Claude Code or Codex, and you want visibility into usage plus the ability to enforce budgets. How can you do that without creating a dedicated API key for every team?
With Agent Network you get a private endpoint inside your network, for example: https://mirror.netbird.ai Teams configure their agents to point to that endpoint instead of using individual API keys directly.
This endpoint is only reachable when users are connected to your NetBird network and authenticated through your IdP. Otherwise, it is not accessible from the public internet. You can then use this private endpoint to configure your AI agents, whether that is Claude Code, Codex, or another tool.
Quickstart
Full step-by-step setup: https://docs.netbird.io/agent-network/quickstart
Architecture
Agent Network is built on two existing NetBird capabilities:
- Overlay network — the encrypted WireGuard mesh between peers.
- Reverse proxy — a NetBird peer that terminates LLM requests, establishes the caller's identity, evaluates policies/limits/guardrails, injects the upstream provider key server-side, forwards to the API or gateway, and records usage.
LLM traffic is routed through the proxy's identity-aware pipeline, while internal resources (databases, internal APIs, self-hosted models) are reached directly over peer-to-peer WireGuard tunnels, governed by the same identities and access policies.
Where the code lives
There is no separate "agent-network" service — it reuses the reverse-proxy and management components:
proxy/— the NetBird reverse proxy that serves the agent network endpoint and runs the per-request middleware pipeline.management/internals/modules/reverseproxy/— the management-side control plane: providers, policies, guardrails, limits, routing, and usage/access logs.
Access roles
Agent Network permissions build on the account permission matrix
(management/server/permissions/). The
agent_network area is split into dotted submodules (agent_network.providers,
.policies, .guardrails, .budgets, .usage, .logs, .settings); a role may
grant a single submodule or the parent, which cascades to all of them.
Two roles delegate Agent Network access without account-admin rights:
agent_network_admin— full control over the wholeagent_networkarea plus read-only users, groups, peers, and account info (needed to build policies). Nothing else in the account.usage_viewer— the regular User baseline plus read onagent_network.usage(the aggregated usage and cost overview). No provider configuration, no policies, no request-level access logs.
Every authenticated user, regardless of role, can read the caller-scoped
self-service endpoints: GET /api/agent-network/me/setup (the endpoint, providers,
and models the caller's own policies allow — what a local AI tool needs and nothing
more) and GET /api/agent-network/me/consumption (the caller's own token and cost
counters). Role definitions live in
management/server/permissions/roles/.
Documentation
Full documentation, architecture, and quickstart: https://docs.netbird.io/agent-network