REMOTE ARC

Usage and costs

Separate Remote Arc limits, user API charges and developer-project costs.

Three independent bills

Remote Arc tool-call entitlement, your AI chat subscription and third-party App usage are separate. Connecting an App does not make its API free. OAuth identifies who authorizes an account; it does not decide who receives the API bill. A user's web subscription can differ from that provider's API plan or credit balance.

Your connected account

Runway uses an API key from your own API project and spends that project's generation credits. WhatsApp uses your Business account, phone number and API credential, with charges following the actual Business billing arrangement. Vercel, Supabase and Linear use OAuth to your account or workspace; their hosting, database or workspace charges still follow that account's plan.

Managed OAuth and platform costs

Remote Arc manages the developer OAuth application for supported providers. Some quotas and fees attach to that developer project even when every user authorizes their own account. X managed OAuth uses Remote Arc's X API project rather than the user's X Premium subscription. Google Workspace has announced project quota and scaled-usage billing changes. Remote Arc also bears hosting, database, credential-management and maintenance costs.

Review the cost-bearing action

A Runway generation shows its requested model, duration and estimated credits before approval. The estimate gate is not a provider-enforced financial cap. Ads APIs can expose spend on the connected advertising account; a report read and an ad purchase are different activities. Hosted Arc inference has a separate budget ledger and is not enabled by connecting Apps. Check current provider pricing and the account's billing controls.