Skip to content

Connectors

A connector is an external-service registration belonging to your wallet: name, base URL, allowed targets and a rotatable agct_ token. Signed-in wallets manage their own registrations under Settings → Developer → Connectors.

Currently a registry only

No platform component validates the token or calls the base URL. Registrations are not used in agent, Legend or Toolset execution. The old v3.30 outbound WebSocket tunnel and connector container were removed. To expose a private-network API, use Embassy.

Web interface

Action Description
Add connector Name up to 100 characters, Base URL and comma-separated Allowed targets. Name and URL are required in the form.
Token Shown once on creation/rotation; server stores bcrypt hash and short agct_ prefix.
Rotate token Creates a new token, immediately invalidating the old one.
Status Never used / Active (last 24 hours) / Idle. No component currently updates last use, so registrations show Never used.
Delete API-only; no web-card button.

API

Method Path Result
GET /api/v1/user/connectors Wallet registrations, newest first, no tokens
POST /api/v1/user/connectors {connector, token}; token only in this response
POST /api/v1/user/connectors/:id/rotate New token
DELETE /api/v1/user/connectors/:id Delete registration

Another wallet's registration returns 404.

Toolset, Connector or Embassy?

Situation Use
Public API with OpenAPI spec or MCP server Toolsets
Private-network API an agent should work with regularly Embassy: runs locally and sends only operator-approved reports
Register an external service and manage its token Connector, currently registry-only