Client-Owned API Keys vs Managed Usage for AI Agents

For CRM, inbox, ecommerce, calendar, finance, HR, SEO, ads, and data-provider accounts, the client should usually own the account and grant AI Team controlled access.

This protects portability, billing transparency, vendor-term compliance, and the client's ability to revoke access.

AI Team can manage standardized model access, run records, long-running work, and operator review when budgets and audit trails are clear.

The model gateway still needs per-client usage tracking, spend thresholds, fallback rules, and records that explain usage.

Any paid external usage should have a provider category, billing method, warning threshold, hard stop, and client approval before the Agent goes live.

A usage policy keeps an affordable subscription from turning into an uncontrolled vendor bill.