Transit Points

Field reference for Transit Points: panel settings and canvas elements for agent-initiated outbound routes on an Agent Surface.

Transit Points define the agent-initiated outbound routes on a surface: the destinations the managed agent is allowed to call through the gateway. The managed agent calls the transit listener. The gateway forwards the call to the configured external endpoint. Use this reference when adding outbound destinations to a surface to understand routing alias requirements and per-destination policy, rate limit, and payment settings.

Transit Point configuration

A single named outbound destination. Configure routing and authentication using the panel settings below. Drop canvas elements on the transit point edge to add capabilities per destination. The same elements available on Access Point and Managed Agent edges apply here, scoped to this destination only.

Each transit point is reachable at:

https://<GATEWAY_HOST>/outgoing/<surface-route>/<alias>/<optional-path>

Or at a custom path when listen_path is set on the transit point.

Panel settings

FieldTypeRequiredDefaultDescription
NamestringNo“Transit Point”Display name shown on the canvas node and in the dashboard. Determines the Routing alias.
Listen AddressdropdownYesOutbound listener host and port for this transit point. Selected from configured outbound listeners.
Channel PrefixdropdownYesPath prefix for the listener URL. Selected from configured channel prefixes.
Custom PathstringYesAuto-generatedPath suffix appended after the channel prefix. Auto-generated as a random path on first drop; editable.
Listener URLstringRead-onlyDerivedAssembled outbound listener URL. Read-only banner.
Routing aliasstringRead-onlyDerivedDerived from the Name field. Forms the path segment in the standard outbound URL: https://<GATEWAY_HOST>/outgoing/<surface-route>/<alias>. Must match ^[a-z][a-z0-9-]*$.
Target EndpointstringYesExternal destination URL (https://). Use the via Gateway Connection option to route to another Trust Gateway instead.
Override Agent Card LocationtoggleNoOffWhen on, overrides the default agent card path for this destination. A2A and AP2 destinations only.
Agent Card LocationstringNo.well-known/agent-card.jsonCustom agent card path relative to the destination base URL. Shown only when Override Agent Card Location is on.
Target AuthenticationselectNoNoneService-level credentials injected into outbound requests. Options: None, Bearer Token, API Key Header, Custom Header.
Inject outbound credentialtoggleNoOffWhen on, pulls a credential from a configured provider and attaches it to every outbound request through this transit point. Expands to show Credential Provider, Scopes, Consent Mode, and Inject As fields.
Require transit tokentoggleNoOnWhen on, every call to this transit point must carry a valid X-Transit-Token header issued by the surface’s Access Point.

Canvas elements

Drop these elements on the transit point edge in the canvas builder. For the complete field reference for each element, see the linked page.

ElementReferenceBehaviour at this position
PolicyOPA policies: Policy elementOPA policy evaluated on requests to this destination before dispatch.
Policy (response)OPA policies: Policy elementOPA policy evaluated on the response from this destination before forwarding back.
Rate LimitNetworking elements: Rate LimitPer-destination request cap.
Trust RegistryTrust registriesVerifies this transit destination against a trust registry before forwarding.
Agent IdentityIdentity elementVP signing and identity extraction for outbound requests to this destination.
Transit Point identityIdentity elementIdentity extraction from this destination’s response. When set, overrides the surface-level external identity slot for this transit point only.
Workload BindingOutbound binding elements: Workload BindingCaller workload identity claims in signed VPs for this destination.
NetworkingNetworking elementsTimeout, retry, and circuit breaker for this destination.
PaymentPayment elementPayment requirements if this destination charges.
Metadata ExtractionMetadata elementsOutbound header mapping from the response. A2A and AP2 destinations only.

URL patterns

The outbound URL shape depends on whether a custom listener path is set on the transit point.

Default path

https://<GATEWAY_HOST>/outgoing/<surface-route>/<alias>/<optional-path>

Custom listener path

https://<GATEWAY_HOST>/<custom-path>/<optional-path>

The /outgoing/... pattern is the standard. Use a custom listener path only when an external system requires a specific path that cannot use the default shape.