Skip to documentation

Connect a provider account

Connect a provider account

Authorize a supported model account, verify it, and enable discovered Models in AnchorShell Pro.

Purpose

Connect a supported provider account. Verify the account and enable selected Models for Relay routing.

Prerequisites

Open Relay → Providers and confirm that the connection type is available. Current types include OpenAI Codex where enabled, OpenRouter where enabled, and supported developer API accounts when that feature is enabled.

You need relay:connections:create:personal for a personal account. You need relay:connections:manage:self to verify, refresh, enable Models, or manage personal access. You need relay:connections:manage:organization for an organization account.

Steps

Subscription Plan Provider

  1. Open Subscription Models.
  2. Select Add subscription plan provider.
  3. Select OpenAI Codex.
  4. Complete the displayed device authorization or supported local pairing flow.
  5. Return to AnchorShell.
  6. Verify the account.
  7. Review the discovered Models.
  8. Enable only the Models that the organization intends to route.

API Key Provider

  1. Open API Key Models.
  2. Select Add provider.
  3. Select an available provider.
  4. Enter the credential in the protected form.
  5. Verify the connection.
  6. Review discovered or configured Models.
  7. Enable the required Models.

OpenRouter can use provider authorization to create an API key. It remains an API Key Provider.

Expected result

The Providers page shows the connected provider and each enabled Model. An enabled Model can join a Standard Group or Smart Group. AnchorShell stores the provider credential in encrypted form.

Verification

Send one controlled request through an enabled Model. Confirm the provider, Model, status, usage, and connection attribution in Relay → Logs.

Recovery

If authorization fails, restart the connection flow and complete it before the transaction expires. If verification fails, confirm the provider account, credential, deployment flag, and provider availability. Do not expose the credential in logs or support messages.

Next

Create an agent User API key and limit.