Trust registry reference

Field reference for the trust registry editor in the Agent Gateway dashboard.

A trust registry connects the gateway to an external authority that determines which agents and issuers are trusted to interact with your surfaces. When a surface receives a request, the gateway queries the assigned registry over a DIDComm connection to check whether the caller’s DID is recognised by that authority.

Use this page to add a registry, monitor its connection state, and confirm reachability before assigning it to a surface.

For conceptual background, see Trust registries.

Fields

FieldEditableDescription
NameYesHuman-readable display name. Appears in Issuer configuration and logs.
DescriptionYesOptional description of the trust registry’s purpose or governance framework.
OOB URLNoThe OOB invitation URL provided by the trust registry administrator. Used to establish the initial DIDComm connection. Set at creation.
DID MethodNoThe DID method used to generate the per-registry identity. Options: Web (did:web), WebVH (did:webvh), or Peer (did:peer). Defaults to Web (did:web). Set at creation and cannot be changed.
Our DIDNoThe gateway’s per-registry DID, created during the OOB handshake. This is the DID the trust registry uses to identify this gateway. Populated after the handshake completes.
Registry DIDNoThe trust registry’s DIDComm identity, discovered during the OOB handshake.
Main DIDNoThe canonical DID of the trust registry. This is the DID that agents reference in their trust-registry extensions (trust_registry_did field). Populated from the OOB invitation.
Mediator URLNoMediator endpoint auto-discovered from the OOB invitation.
Connection StatusNoCurrent connection state. See Connection statuses.
StatusYes (via delete/recreate)active or disabled. Disabled registries are excluded from Issuer configuration.

Connection statuses

StatusMeaning
CONNECTINGThe OOB handshake is in progress.
AWAITING APPROVALSetup message sent. Waiting for the trust registry administrator to approve.
CONNECTEDConnection is established. TRQP queries can be issued.
DISCONNECTEDPreviously connected. Use Reconnect to re-establish.
FAILEDConnection failed. Use Reconnect to retry.

Actions

ActionAvailable whenDescription
ReconnectStatus is DISCONNECTED or FAILED.Re-initiates the DIDComm handshake using the stored OOB URL.
HeartbeatStatus is CONNECTED.Sends a test query to confirm the connection is live. Returns Ping to "<name>" successful (<ms>ms) on success.