The provider connections an agent release may run on
Lists the enabled provider connections of the installation by id, with kind, billing and the models an agent's card may name on each, and model_successors: each model the connection dropped that has a later model of its series listed, which a session on the dropped one moves to. A release names one of them as connection_id and runs the card's model on it. Never an endpoint or credential. Any member of the workspace reads it.
Scope: sessions:read (API key or cookie session).
AuthorizationBearer <token>For servers and scripts: an API key sent as an HTTP bearer token, Bearer <key>. It holds exactly the scopes it was issued with; a key issued before scopes existed holds none. It never needs the CSRF header, and it cannot manage agents, members, teams or API keys. Issue one in the web console under Settings → API keys; each operation names the scope it needs.
Scope: sessions:read
The enabled connections ordered by id.
application/json- response
items*array<>curl -X GET 'https://example.com/v1/connections'{ "items": [ { "id": "anthropic-main", "kind": "anthropic", "billing": "metered", "models": [ "claude-sonnet-5", "claude-haiku-5" ], "model_successors": {} } ]}