What disabling a connection would leave without a model
The operator (installation.settings.manage, the workspace owner), signed in; an API key is 403 whatever its scopes. Counts, read when the confirmation opens: the current profile versions with no other enabled connection that fits once this one is gone (the whole installation, any workspace's derived version included), the active agents whose active release runs one of them, the sessions not yet failed or stopped that run one of them, and whether a workspace's achievement judge setting names the connection. Counts only, no names. Changes nothing; disabling is never blocked by it. 404 for an id the console does not hold.
Auth: cookie session only; no scope.
cookieSession__Host-werft_session<token>For the web console: the browser session cookie set by POST /v1/auth/login. It holds the scopes of the user's workspace role (owner: all; admin and member: all but sessions:recover). Requests other than GET must also send X-Requested-With: werft-web.
id*stringThe model connection's id.
1 <= lengthThe counts for the connection.
application/json- response
id*string1 <= lengthprofile_count*integer0 <= value <= 9007199254740991agent_count*integer0 <= value <= 9007199254740991session_count*integer0 <= value <= 9007199254740991judge_used*booleancurl -X GET 'https://example.com/v1/installation/settings/connections/string/impact'{ "id": "anthropic-console", "profile_count": 2, "agent_count": 3, "session_count": 1, "judge_used": false}