Connections.

Open this deployment's console and connections.

Choose a service

The reference catalog shows current implementations. Actual availability is determined by your workspace's published catalog.

Authorize an account

Check the service address and required permissions before approving. OAuth connections use the provider's page; API keys are entered through the secure connection flow.

Check the state

After returning to Context4, check the connection status. If there is an error, read the message and retry after resolving its cause. Do not send secrets to support.

Multiple accounts

If the agent finds multiple connections, identify the intended one by its safe identifier and purpose. Do not automatically select the first account. Sharing is explicit and checked during execution, including tenant and principal; another user's connection does not become accessible merely because it is visible in the same organization.

States

pending means an unfinished connection, active means the account is ready, degraded means limited operation, failed means an error and revoked means access was withdrawn. Active does not guarantee permission for every provider API method. For OAuth/credential flows, use the Context4 link and enter secrets only in the designated form.

A server integration can use its own OAuth auth config. The native API supports renewing authorization for an OAuth connection that has not yet become active, with version checking; this is not a universal refresh button for any account. HTTP contracts define the exact conditions and fields.