ShareAI Platform Docs

Disconnect an application or client service

Disconnect an authorized application or service, stop new AI requests, and keep your spending history.

View as Markdown
On this page

If a client-work service should no longer use your workspace, open its current commitment and review the available Disconnect action. Closing a browser tab does not revoke the service.

Example connected service with monthly spending, a fifty-euro limit, model pricing and Disconnect controls.Example connected service with monthly spending, a fifty-euro limit, model pricing and Disconnect controls.
Example connection: the paying account controls its monthly AI limit and can disconnect the service.

Review before stopping#

  1. Open Billing → Subscriptions & Commitments in the paying workspace.
  2. Select the work and confirm its Builder and current status.
  3. Read the Disconnect explanation and use the explicit confirmation when you intend to stop access.
  4. Verify the resulting state and check History and Activity & Decisions.

Previous usage remains#

Stopping future authorization does not erase previously recorded consumption, decisions or purchases. Check Usage for the relevant period when reconciling charges.

A client-work Production credential, a normal Console API key and an application OAuth grant have separate lifecycles. Revoke the authorization that actually powers the service. Deleting an unrelated personal key does not necessarily stop a Builder integration.

When the action is unavailable#

Confirm your role and workspace and contact the Builder or support with the work reference. Do not use another account to bypass an organization’s approval boundary.

Monthly spending limits and billing recovery#

Each paying account can set its own monthly AI spending limit per application or client service in Billing → Subscriptions & Commitments. The cap includes network cost and builder surcharge, while fixed subscriptions and confirmed purchases stay separate. A cap error uses HTTP 402 application_spending_limit_exceeded; insufficient eligible credits use HTTP 402 insufficient_credits. Both provide a customer billing link. Error contract, streaming handling and integration example.

Last updated September 18, 2026

ShareAI Platform Docs
All documentation

Search by title or content.

Ask about this page

Choose an assistant to explore this page. You can also copy the page and paste it into your conversation.

Ask ChatGPTAsk ClaudeAsk GrokAsk ShareAI