Your OAuth token might be a terms violation waiting to happen.

Short answer: OpenAI, Kimi, Google Gemini API, and most providers allow OpenClaw. Anthropic and Google OAuth (Antigravity) explicitly ban it with account suspension risk. Use the 10-second check below to find your provider’s status and migration path if needed.


10-Second Status Check

Find your provider and your verdict:

ProviderCan I Use OpenClaw?RiskDetectionAction Needed
Anthropic Claude⚠️ YES — Usage bundles required🟡 MEDIUMBilling enforcement from April 4, 2026See new options →
Google OAuth (Antigravity)NO — Blocked🔴 HIGHOAuth token revocationUse API keys →
Google Gemini APIYES — Allowed🟡 LOW-MEDIUMGoogle’s platform patternUse with caution →
OpenAIYES — Allowed🟢 LOWNone reportedContinue safely →
Kimi k2.5YES — Open source🟢 LOWNone (weights available)Best free option →
AWS BedrockYES — Enterprise OK🟢 LOWNone reportedContinue safely
Together AIYES — BYOK friendly🟢 LOWNone reportedContinue safely
Fireworks AIYES — BYOK friendly🟢 LOWNone reportedContinue safely
Self-hostedYES — You’re the provider🟢 NONEN/AUltimate escape →
GroqYES — With caveats🟡 MEDIUMStay within rate limitsSee guidelines →
Azure OpenAIYES — Enterprise OK🟡 MEDIUMGovernance requiredSee requirements →
CerebrasYES — Allowed🟢 LOWInfrastructure providerSee details →
PerplexityYES — With caveats🟡 MEDIUMDon’t build competing searchSee guidelines →
Mistral AIYES — Explicitly supported🟢 LOWMCP named in termsSee details →

Don’t see your provider? Check the full matrix below or read OpenClaw provider policies.


Background: The March 2026 Rate Limit Changes

Before the April 4 OpenClaw policy shift, Anthropic implemented peak-hour throttling on March 26, 2026:

AspectDetails
Affected hoursWeekdays 5am–11am PT / 1pm–7pm GMT
Change5-hour session limits burn faster during peak hours
Weekly limitsUnchanged — only allocation across week shifted
Impact~7% of users hit limits they wouldn’t have before

This was Anthropic’s first capacity management response before the full OpenClaw policy change. Users reported hitting limits “way faster than expected” — some suspected a bug, but Anthropic confirmed it was intentional to manage demand.


The Breaking Story: Google Joins the Crackdown

Between February 9-23, 2026, Google suspended Antigravity AI IDE access for users who authenticated third-party tools via OAuth. AI Ultra subscribers ($249.99/month) lost access without warning.

The trigger: Section 6 of Antigravity’s Additional Terms of Service:

“You must not abuse, harm, interfere with, or disrupt the Service. This includes, but is not limited to, using the Service in connection with products not provided by us.

Google DeepMind engineer Varun Mohan confirmed on X (February 22, 2026):

“We’ve been seeing a massive increase in malicious usage of the Antigravity backend that has tremendously degraded the quality of service for our users. We needed to find the path to quickly shut off access to these users that are not using the product as intended.”

Critical distinction: Google is only blocking Antigravity access, not your entire Google account. Per the Google DeepMind spokesperson (VentureBeat, February 23, 2026):

“The move is not to permanently ban the use of Antigravity to access third-party platforms, but to align its use with the platform’s terms of service.”

Recovery path exists: Varun Mohan explicitly stated that “users not aware that this was against our ToS will get a path for them to come back on.”

March 2026 update: Recovery process confirmed via [email protected]. Eligible users (first-time violation, unaware of ToS, immediate cessation) are seeing 1-2 week response times. Billing issues during suspension remain unresolved.

See Google Antigravity terms verification for full ToS analysis and Google Antigravity OAuth risk for risk assessment.


The Pattern Anthropic Started (January 2026)

This isn’t new. Anthropic deployed the same pattern starting January 9, 2026.

The policy (now in writing):

“Using OAuth tokens obtained through Claude Free, Pro, or Max accounts in any other product, tool, or service — including the Agent SDK — is not permitted and constitutes a violation of the Consumer Terms of Service.” — Anthropic Claude Code Legal and Compliance, February 2026

The impact: OpenCode, Roo Code, and dozens of agent frameworks lost their core value proposition overnight.

For full timeline and economic analysis, see Anthropic’s OAuth Policy, Now in Writing.


Enforcement Comparison: Google vs Anthropic

AspectAnthropicGoogle
MethodAPI error with rejection messageAntigravity access suspension
Account impactIntactOnly Antigravity blocked (Gmail OK)
BillingSubscription continues normallyContinues during suspension
Reversal policyAccidental bans reversedRecovery path for unaware users
CommunicationPublished legal page (Feb 19)X post + VentureBeat interview
DocumentationOfficial policy pageForum posts + spokesperson

Both providers ban the same pattern: routing subscription OAuth tokens through third-party tools. The enforcement style differs, but the risk is the same — loss of access.


OpenAI: The Marketplace Exception

While Anthropic and Google build walls, OpenAI built bridges. Their Codex CLI explicitly supports ChatGPT Plus/Pro OAuth — the exact pattern Anthropic banned.

Why this is safe:

  • ✅ OAuth from ChatGPT subscriptions is explicitly documented
  • ✅ Codex CLI proves automation is intended architecture
  • ✅ No agent tool enforcement reported

Verdict: 🟢 LOW RISK — Continue using OpenAI with OpenClaw.


Kimi k2.5: The Open-Source Escape Hatch

Why Kimi is the safest bet:

  • Open-source weights — Even if API banned, you can self-host
  • 8x cheaper than Claude ($3/1M vs $25/1M output tokens)
  • 76.8% SWE-bench — 80% of Claude Opus 4.5’s performance
  • Free via OpenCode Zen

Verdict: 🟢 LOWEST RISK — Ideal migration target from Anthropic.


Already Using a Banned Provider?

Already Using Anthropic + OpenClaw?

Update April 2026: Anthropic has shifted from a ban to a pay-as-you-go model. You now have options:

Option 1: Usage Bundles (New)

  • Anthropic is offering “discounted usage bundles” for third-party tool access
  • Discount: Up to 30% off when pre-purchasing
  • Billed separately from your subscription
  • One-time credit equal to monthly plan cost being provided automatically
  • ⚠️ Credit expires April 17, 2026 — redeem by this date

Real-world costs (based on user reports):

Usage LevelOld CostNew Cost
Light$20/mo$20-50/mo
Moderate$100/mo$100-300/mo
Heavy$200/mo$500-1000+/mo

Option 2: Switch to API Keys

  1. Generate API key from Claude Console
  2. Update OpenClaw config to use API key instead of OAuth
  3. Metered pricing (higher cost for heavy usage)
  4. Most compliant path
  5. Benefit: Boris Cherny (Head of Claude Code) submitted PRs to improve OpenClaw’s prompt cache efficiency — API users benefit from these optimizations

Option 3: Request Refund

  • Anthropic offering full refunds for subscribers who prefer to cancel
  • Contact Anthropic support to request

Option 3: Migrate to Another Provider

  • Kimi k2.5: 8x cheaper, no restrictions (migration guide below)
  • OpenAI: Explicitly allows third-party OAuth via Codex CLI

If you were banned in Jan/Feb 2026 (before April policy change):

  • Appeal: Reply to ban email with usage explanation
  • Success rate: Anthropic reversed ~30% of false positives (January 2026)
  • Don’t evade: Creating new accounts violates terms further
  • Document: Screenshot the ban notice for your records

Timeline: Appeals take 5-10 business days. Have a backup provider ready.


Already Using Google OAuth + Antigravity?

Scope check (critical distinction):

ServiceStatus
❌ Antigravity OAuthBlocked (February 2026 enforcement)
✅ Your Google AccountNot at risk — only Antigravity affected
✅ Gmail/WorkspaceUnaffected
✅ Other Google servicesUnaffected

Immediate steps:

  1. Stop OAuth sign-in to Antigravity
  2. Switch to Gemini API keys: Use Google AI Studio or Vertex AI
  3. Contact support: [email protected]
  4. Document the error: Screenshot any “access denied” messages

Recovery path:

Google is reportedly allowing “unaware user” recoveries for:

  • First-time violation
  • Immediate cessation
  • Account in good standing

Response time: 1-2 weeks (based on forum reports)


The Data Loss Risk Nobody Talks About

This is the scary part. When you get banned, you might lose more than just API access—you could lose your work, your context, your accumulated knowledge.

What You Could Lose

Data TypeWhat’s At RiskCan You Recover It?
Conversation HistoryPast chats, code reviews, debugging sessions❌ Usually lost on ban
Custom Instructions/MemoriesClaude’s “memory” of your preferences❌ Lost if account suspended
Projects & ArtifactsCode generated, files created, analyses⚠️ Only if you saved locally
Custom Skills/PromptsYour personalized OpenClaw configurations✅ Usually safe (local)
API Keys & ConfigsIntegration settings, connected services✅ Can recreate

The Harsh Reality: Export After Ban?

Anthropic:

  • No self-service export during suspension
  • ⚠️ Some users report being able to request data export during appeal
  • ❌ OAuth-dependent tools lose all context immediately

Google Antigravity:

  • Gmail/Drive unaffected — only Antigravity suspended
  • Antigravity conversation history lost — no export path
  • ⚠️ Recovery path confirmed March 2026; 1-2 week timeline for eligible cases

Proactive Protection: Do This NOW

Don’t wait for a ban. Protect your data today:

1. Export Regularly (Set a Calendar Reminder)

Anthropic users:

Claude.ai → Settings → Data Export → Request Download
  • Export includes: Conversations, memories, account data
  • Takes 24-48 hours to generate
  • Do this monthly if you rely on Claude for work

Antigravity users:

  • No built-in export for conversation history
  • Screenshot or copy critical conversations manually
  • Use Gemini API keys instead (allows programmatic access)

2. Maintain Local Backups

OpenClaw configuration:

1
2
3
4
5
# Back up your settings
cp ~/.config/openclaw/settings.json ~/backups/openclaw-$(date +%Y%m%d).json

# Back up custom skills
cp -r ~/.config/openclaw/skills ~/backups/skills-$(date +%Y%m%d)

Important projects:

  • Don’t rely on provider “projects” or “artifacts”
  • Save generated code to local git repos
  • Use GitHub/GitLab for anything you can’t afford to lose

3. Diversify Your AI Usage

Don’t put all your eggs in one basket:

  • Use multiple providers for different tasks
  • Keep local LLM options ready (Ollama, etc.)
  • Maintain portable prompts that work across models

4. The Nuclear Option: Full Migration

If you’re at high risk (using banned providers):

1
2
3
4
5
# 1. Export everything possible
# 2. Switch to Kimi or OpenAI
# 3. Document your critical workflows
# 4. Test the new provider thoroughly
# 5. Only then revoke old API keys

Master Provider Matrix

ProviderOpenClaw StatusAuth MethodBan RiskMonthly Cost*Migration Difficulty
Anthropic⚠️ Usage bundlesOAuth + bundles🟡 MEDIUM$200+ bundlesNew options available
Google OAuth🚫 OAuth blockedOAuth only🔴 HIGH$20-250Easy — use API keys
Google Gemini API✅ AllowedAPI key🟡 LOW-MEDIUMFree-$20Caution advised
OpenAI✅ AllowedOAuth/API🟢 LOW$20-200None needed
Kimi k2.5✅ AllowedAPI🟢 LOW$0-50Easy
AWS Bedrock✅ AllowedAPI🟢 LOWVariableNone needed
Together AI✅ AllowedAPI🟢 LOWVariableNone needed
Fireworks AI✅ AllowedAPI🟢 LOWVariableNone needed
Self-hosted✅ AllowedLocal🟢 NONEHardware costHard
Groq✅ Allowed*API🟡 MEDIUMVariableGuidelines
Azure OpenAI✅ Allowed*API🟡 MEDIUMVariableRequirements
Cerebras✅ AllowedAPI🟢 LOWVariableDetails
Perplexity✅ Allowed*API🟡 MEDIUMVariableGuidelines
Mistral AI✅ AllowedAPI🟢 LOWVariableDetails

*Monthly cost = typical developer usage. See Smart Spend Guide for detailed breakdowns.


Migration Guide

Anthropic to Kimi k2.5 (Recommended)

  1. Export config: cat ~/.config/openclaw/settings.json
  2. Get Kimi API key: platform.moonshot.cn
  3. Update endpoint: api.anthropic.comapi.moonshot.cn
  4. Update model: claude-3-7-sonnet-20250219kimi-k2.5
  5. Test: Run a small task first
  6. Decommission: Revoke Anthropic key when confident

Cost impact: $200-1000+/month (Anthropic) → $0 (NVIDIA NIM / OpenCode Zen) or $10-50/month (Kimi API) = 80-100% savings


Google OAuth to Google API

Same provider, compliant path.

  1. Get API key: Google AI Studio
  2. Update config: Replace OAuth flow with API key
  3. Test: Verify access works
  4. Appeal (if suspended): Contact support with compliance evidence

Cost impact: Same pricing — you’re changing auth method, not provider.


The Ultimate Escape: Self-Hosted

Zero provider risk. You are the provider.

Best for: Banned users, high-volume usage, privacy-sensitive workloads.

Trade-offs:

AspectSelf-HostedAPI Provider
CostUpfront GPU/RAMPay-as-you-go
CapabilitiesOpen models onlyFrontier models
Terms riskZEROVaries
ComplexityHigherLower

Options: Ollama, llama.cpp, vLLM. See Self-hosting guide.


The Bigger Pattern

DateVendorActionImpact
2025-06AnthropicCuts Windsurf capacityThird-party restrictions begin
2025-08AnthropicRevokes OpenAI API accessCompetitive benchmarking blocked
2026-01AnthropicOAuth harness blockOpenCode, Roo Code broken
2026-02AnthropicPolicy formalization“Walled garden” documented
2026-02GoogleAntigravity OAuth blockMirrors Anthropic pattern
2026-02-25AnthropicDOD pressure / Hegseth ultimatumMilitary use policy under threat
2026-04-04AnthropicPay-as-you-go modelSubscription limits no longer cover third-party tools; usage bundles introduced

Provider philosophy comparison:

VendorPhilosophyOpenClaw Risk
AnthropicWalled garden🔴 HIGH — Explicit ban, technical enforcement
GooglePlatform control🔴 HIGH — OAuth blocked, API still OK
OpenAIMarketplace🟢 LOW — Codex CLI uses same pattern
KimiOpen source🟢 LOW — Weights available, BYOK friendly

The lesson: Platform dependency is risk. The providers that allow OpenClaw today offer genuine alternatives.


FAQ

Q: Can Anthropic/Google detect OpenClaw usage?

A: Yes. Both analyze request patterns, client identifiers, usage characteristics. Google used “User-Agent and binary signature analysis.” Anthropic uses “client fingerprinting via HTTP headers.”

Q: Is there any way to use Claude with OpenClaw legally?

A: Only via commercial API (Console, Bedrock, Vertex). Consumer plans (Free/Pro/Max) are blocked for third-party tools.

Q: Will other providers follow Anthropic/Google?

A: Unlikely for open-source-friendly providers (Kimi, Together, Fireworks). Google and Anthropic share a pattern of tight platform control. OpenAI’s marketplace approach differs.

Q: What about BYOK services (Together, Fireworks)?

A: BYOK shifts responsibility to you. The inference provider generally doesn’t restrict client tools — your risk is with the underlying model provider.

Q: I got banned from Google — will I lose Gmail?

A: No. Only Antigravity is suspended. Gmail, Drive, and other Google services remain functional.


Breaking Coverage:

Security & Risk:

Migration & Setup:

Anthropic Context:

Provider Verification Deep Dives:


Sources

Primary Sources

News Coverage

Analysis


Last updated: 2026-04-06
Next review: 2026-05-06 (monthly during policy volatility)
Policy pages change. Verify current terms at official sources before making architectural decisions.