Access Point
The Access Point is the inbound listener node on an Agent Surface. It defines the URL callers use to reach the managed agent and controls routing at the surface entry point.
Every surface has exactly one Access Point. The Listen Address, Surface Prefix, and Custom Path panel fields together form the base URL callers use to reach the surface. The protocol is set at the surface level; see Protocol options.
Panel settings
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| Name | string | No | “Access Point” | Friendly display name shown in the dashboard (for example in monitoring slice pickers). Has no effect on routing. |
| Listen Address | dropdown | Yes | — | Gateway listener this Access Point binds to. Populated from the gateway’s configured inbound addresses. |
| Surface Prefix | dropdown | Yes | — | Route namespace prefix. Populated from the gateway’s configured surface prefixes. Combined with Custom Path to form the full route. |
| Custom Path | string | Yes | Auto-generated | Path segment appended to the Surface Prefix. Must not contain .. segments. |
| Channel Route | string | Read-only | Derived | Assembled route displayed as the Access Point URL. Read-only banner. |
A2A surfaces only
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| Primary extension URI | string | No | None | Primary A2A extension URI used for dashboard display and metrics grouping. |
| Supported extensions | string, comma-separated | No | [] | A2A extension URIs advertised in the agent card. |
| Override Agent Card Location | toggle | No | Off | When on, overrides the default agent card path. |
| Agent Card Location | string | No | .well-known/agent-card.json | Custom agent card path relative to the managed agent base URL. Shown only when Override Agent Card Location is on. |
Canvas elements
These canvas elements add capabilities at the inbound pipeline stage, before a request reaches the managed agent. Each one attaches to a specific edge, either the Caller → Access Point edge (before the request reaches the Access Point) or the Access Point → Managed Agent edge itself. The Behaviour column below states each element’s actual edge; see the linked reference page for the full placement detail.
| Element | Reference | Behaviour at this position |
|---|---|---|
| Policy | OPA policies: Policy element | Attaches to the Caller → Access Point edge as the inbound policy variant. Evaluated before the request reaches the Managed Agent. |
| Rate Limit | Networking elements: Rate Limit | Attaches to the Caller → Access Point edge. Inbound request cap applied at the surface entry point. |
| Caller Context | Caller Context reference | Attaches to the Caller → Access Point edge. Authentication method selection and per-method credential extraction configuration. |
| Identity | Identity element reference | Attaches to the Caller → Access Point edge for inbound caller identity, or to the Access Point → Caller response edge for protected agent identity (the managed agent’s own DID, extracted from its reply). See the linked reference for the full slot list. |
| Trust Check | Trust elements reference | Attaches to the Access Point → Managed Agent edge as the caller leg. Per-element TRQP verification on the caller leg. Results appear as input.trust_check_results.caller in OPA evaluation. |
| Extension Validation | Protocol extensions reference | Attaches to the Access Point → Managed Agent request edge. Schema validation applied to inbound request payloads. A2A surfaces only. |
| Metadata Extraction | Metadata elements reference | Attaches to the Access Point → Managed Agent request edge on A2A surfaces. Header-to-metadata mapping at the access point boundary. Disabled on MCP surfaces, where the header mapping editor does not appear. |
Related
- Surface reference: Top-level surface fields, protocol options, and gateway DID injection settings.
- Managed Agent reference: Upstream endpoint and authentication fields.
- Caller Context reference: Authentication method options and per-method credential extraction configuration.
- Trust elements reference: Full field reference for Trust Check elements, query parameters, template syntax, and result wire shape.
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.