Managed Agent
The Managed Agent node defines the single upstream destination the gateway forwards traffic to. Every surface has exactly one Managed Agent. The properties panel covers endpoint routing and authentication. Policy enforcement, networking resilience, MCP tool access policies, Trust Check queries, and identity extraction each require a separate canvas element added to the surface. Reference pages for each element are linked from the canvas table below.
Managed Agent node fields
These fields appear directly in the Managed Agent properties panel when you select the node on the canvas.
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| Endpoint Type | select | Yes | Direct URL | How the upstream destination is addressed. Options: Direct URL, via Gateway Connection, via MCP Proxy (MCP surfaces only), via A2A Proxy (A2A surfaces only). |
| Target Endpoint URL | string | Yes (Direct URL) | — | Full upstream URL. See Endpoint schemes. |
| Gateway / Agent Surface on Gateway | select | Yes (via Gateway Connection) | — | Remote gateway and the agent surface on it to route to. Builds a fabric:// endpoint automatically. |
| MCP Proxy | select | Yes (via MCP Proxy) | — | MCP proxy to front this agent’s tools. Builds a proxy:// endpoint automatically. |
| A2A Proxy | select | Yes (via A2A Proxy) | — | A2A proxy backend for this surface. Builds an a2a-proxy:// endpoint automatically. |
| Display name | string | No | — | Cached name shown in the dashboard for fabric:// endpoints when the remote gateway is offline. |
| Target Authentication | select | No | None | Service-level credentials the gateway injects into requests forwarded to the target. Options: None, Bearer Token, Basic Auth, API Key, Custom. Not available on MCP Proxy or A2A Proxy endpoint types. |
| Send signed identity VP to target | bool | No | true | When enabled, the gateway signs and injects a Verifiable Presentation into each outbound request carrying the resolved agent identity and caller context. See Identity element reference. |
An MPP Auto-Pay section appears in this panel when the Target Endpoint URL uses the fabric:// scheme, on a gateway build with the MPP payment feature enabled. It is not present on the standard managed-hosting dashboard; a self-hosted deployment enables it by building the dashboard with REACT_APP_ENABLE_MPP_PAYWALL=true.
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| Automatically pay MPP challenges | bool | No | Off | Automatically pays an MPP payment challenge from a fabric:// target without requiring the original caller’s involvement. |
| Max amount per request | string | No | — | Shown when auto-pay is on. Safety cap on the amount auto-paid per request, for example 0.01. |
Canvas elements on the Managed Agent
The following elements can be added to the surface from the element palette. Each appears as its own node on the canvas and attaches to the Managed Agent’s edges.
| Element | Description |
|---|---|
| Caller Context | Extracts caller authentication context from inbound callers (JWT, API key, DID Auth, mTLS). See Caller Context element reference. |
| Policy | OPA policy evaluation gate. Can be placed on the request or response edge. See Policy element reference. |
| Rate Limit | Per-route or per-caller request rate limiting. See Rate Limit element reference. |
| Payment | x402 or MPP paywall (MCP and A2A surfaces only). See Payment element reference. |
| Identity | Extracts agent DID from inbound or outbound traffic for VP stamping. See Identity element reference. |
| Trust Check | Runs a TRQP authorisation or recognition query against a trust registry. See Trust registry elements reference. |
| Trust Recorder | Writes agent-registration records into one or more trust registries. See Trust registry elements reference. |
| Extension Validation | Requires and validates protocol extensions on requests (A2A only). See Protocol extension elements reference. |
| Extension Rules | Allows, strips, or rejects protocol extensions per URI (A2A only). See Protocol extension elements reference. |
| Metadata Injection | Injects custom request or response headers, extensions, or body fields. See Metadata elements reference. |
| Metadata Extraction | Maps request headers into protocol metadata before downstream controls run. See Metadata elements reference. |
| Credential Delegation | Injects outbound credentials for upstream calls. See Outbound binding elements reference. |
| Workload Binding | Binds managed-agent identity and caller context into the outbound VP for a Transit Point. See Outbound binding elements reference. |
| Per-tool policy bindings | Per-tool OPA policy bindings configured on the node labelled MCP Proxy in the synthesised chain, not a draggable canvas element. See Per-tool policy bindings reference. |
| MCP Tool Gating | Regex-based allow/deny firewall over MCP tool names, applied to both tools/list and tools/call (MCP surfaces only). See MCP Tool Gating element reference. |
| Networking | Timeout, retry, circuit breaker, and traffic mirroring. See Networking element reference. |
Endpoint schemes
| Scheme | Format | Use case |
|---|---|---|
| HTTPS | https://<host>:<port>/<path> | Standard HTTP/S upstream target. |
| Fabric | fabric://{gateway_id}/{surface_id} | Gateway-to-gateway routing through the fabric. |
| Proxy | proxy://{mcp_proxy_id} | Routes through a configured MCP proxy backend. Requires mcp_proxy_id. |
| A2A Proxy | a2a-proxy://{a2a_proxy_id} | Routes through a configured A2A proxy backend. Available on A2A surfaces. |
Related
- Access Point reference: Inbound configuration and caller authentication.
- Transit Points reference: Agent-initiated outbound routes.
- Trust registry elements reference: Full field reference for Trust Check and Trust Recorder elements.
- OPA policies concepts: How gateway and surface-level OPA policies are evaluated.
Glad to hear it! Please tell us how we can improve more.
Sorry to hear that. Please tell us how we can improve.
Thank you for sharing your feedback so we can improve your experience.