Use existing AI subscriptions
© 2026 Quadropic Pvt Ltd. Proprietary and confidential. Use restrictions.
Syntheo can connect to eligible existing AI subscriptions through provider OAuth. This is different from entering a developer API key.
Subscription or API key?#
| You already pay for | Select this provider in Syntheo | Authentication | Important distinction |
|---|---|---|---|
| Claude Pro or Max, including eligible Claude/Claude Code access | Anthropic | Switch Key to OAuth, then Authenticate | Anthropic API-key billing is separate |
| ChatGPT Plus or Pro with eligible Codex access | OpenAI Codex | OAuth, then Authenticate | The regular OpenAI provider uses API-key billing |
| GitHub Copilot | GitHub Copilot | OAuth, then Authenticate | Model access follows the Copilot account |
| Provider developer/API account | That provider’s regular entry, such as OpenAI or Anthropic | Key | Usage is charged under the provider’s API terms |
Eligibility, models, limits, regions, and subscription terms are controlled by the provider and can change. Syntheo does not convert a consumer subscription into API credit or bypass provider limits.
Connect a Claude or Claude Code subscription#
Use this path when you want Syntheo to use an eligible Claude Pro/Max account instead of a separately billed Anthropic API key.
- Open Settings → AI Provider.
- In the model lane you want to configure, choose Anthropic.
- Choose an available Claude model.
- In the Anthropic authentication controls, switch from Key to OAuth.
- Choose Authenticate.
- Complete the Anthropic sign-in and authorization flow using the account that owns the subscription.
- Return to Syntheo and wait for the connected/ready status.
- Send a small Ask request to confirm access.
This authorizes Syntheo through the supported Anthropic OAuth flow. It does not require copying an API key, and it does not merely reuse an arbitrary local Claude Code CLI process or terminal session.
To use the same subscription for several lanes, assign Anthropic to Standard, Hunter, Light, Design, or Browser as needed. Authenticate the provider once; lanes using that provider reuse the connected account.
Connect a ChatGPT Plus or Pro subscription#
Use OpenAI Codex, not the regular OpenAI provider, when you want eligible subscription-backed Codex access.
- Open Settings → AI Provider.
- Choose OpenAI Codex for the desired model lane.
- Select an available Codex model.
- Keep authentication on OAuth.
- Choose Authenticate.
- Sign in with the ChatGPT account that owns the eligible Plus or Pro subscription.
- Complete authorization and return to Syntheo.
- Run a small Ask or Submit request.
The regular OpenAI provider expects an OpenAI API key and uses the developer API account. A ChatGPT subscription by itself is not an API key.
You may assign OpenAI Codex to multiple Syntheo lanes and reuse the same connected account. Choose model and thinking settings per lane so quick work does not automatically consume the strongest configuration.
Connect GitHub Copilot#
- Choose GitHub Copilot in a model lane.
- Choose the model offered for your account.
- Authenticate with OAuth.
- Complete GitHub’s verification flow.
- Test with a small request.
Access follows the signed-in Copilot account and its enabled models. If a model is rejected as unsupported, enable or select it in the provider’s normal Copilot model controls, then retry or choose another offered model.
Reuse one connection across model lanes#
Credentials belong to the provider connection, not to an individual lane. A practical subscription-first setup is:
| Lane | Example connection choice |
|---|---|
| Standard | Subscription-backed provider with balanced model |
| Hunter | Same provider, strongest eligible reasoning/code model |
| Light | Same provider, fastest eligible model |
| Design | Same provider or a vision/design-oriented model |
| Browser | Same provider or a model reliable with web/tool tasks |
You authenticate only the provider connection. Each lane still retains its own model and thinking-level selection.
When an API key is still better#
Use a developer API key when:
- the subscription OAuth provider does not offer the model you need;
- work belongs to a company API account rather than a personal subscription;
- you need separate billing, quotas, audit ownership, or revocation;
- the workload runs under organizational API terms;
- provider policy does not permit the intended subscription use;
- you need a custom endpoint or proxy.
Never use a personal subscription for organizational work when policy requires a company-managed account.
Billing and account safety#
- Provider subscriptions and developer API billing are separate products unless the provider explicitly says otherwise.
- OAuth access remains subject to subscription usage limits, provider policy, and model availability.
- Authenticate only in the provider-controlled page or device-code flow opened by Syntheo.
- Never paste passwords, recovery codes, session cookies, or OAuth tokens into a task.
- Use Disconnect in AI Provider settings to remove a connected account from Syntheo.
- Reconnect after changing account, subscription, or organization.
- Use separate provider accounts where organizational policy requires separation.
Troubleshoot subscription access#
OAuth option does not appear#
- Confirm you selected Anthropic, OpenAI Codex, or GitHub Copilot.
- The regular OpenAI provider is key-based.
- Refresh the provider catalog or restart Syntheo if provider controls are stale.
Sign-in succeeds but the model fails#
- Confirm the signed-in account owns the required subscription.
- Select a model actually available to that account.
- Check provider region, organization, and usage limits.
- Disconnect and authenticate again if the account changed.
- Try a small request before diagnosing a large task.
OAuth token needs attention#
Use the refresh control. If refresh fails, Disconnect and authenticate again. Do not fall back to pasting tokens into the API-key field.
Unsure which account is active#
Disconnect, then authenticate again in a private/incognito browser session or after signing out of other provider accounts. Verify the account shown on the provider’s authorization page before approving.