Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The September 10 release note explicitly removes the specified billing-email restriction and extends PAYG subscription and AI developer-tool eligibility to all projects linked to invoiced Cloud Billing accounts.
- Google gives a release date without an exact time or time zone. Account-level rollout, console visibility and automatic activation remain UNKNOWN.
- Eligibility to subscribe or access does not mean every project has purchased an edition, assigned licenses, enabled features, met regional requirements or obtained IAM permissions.
- Some linked documentation still requires the specified email. Record the policy change from the newer release note while preserving the conflict, and verify through the actual console or a support ticket.
- AI developer tools cover surfaces including Antigravity, Antigravity for IDEs and Android Studio. New and existing subscriptions have different activation paths.
- Edition, billing, license, IAM and rollout issues are not network faults. A fixed exit cannot confer eligibility, enable tools or change official prices.
What changed: the specified email requirement ended on September 10
The September 10, 2026 Gemini Enterprise release note says subscribing to Pay-as-you-go edition and accessing AI developer tools are now available to all projects linked to invoiced Cloud Billing accounts. Previously only customers receiving an email titled [Billing Update] New Gemini Enterprise overage billing controls launching Aug 17, 2026 could access developer tools. Google explicitly says that restriction no longer applies.
The entry gives a date without an exact time or time zone; do not invent midnight Beijing time. This is separate from the September 1 overage-control change: September 10 concerns PAYG subscriptions and developer-tool eligibility, while September 1 concerns switches that allow continued billing beyond pooled quotas on seat-based editions.
“All projects” does not mean automatic activation
The release note's “all projects linked to an invoiced Cloud Billing account” removes the specified email gate. It does not create subscriptions, assign licenses, enable regional features or grant roles. Administrators should record project ID, billing-account type, valid monthly invoice receipt, Gemini Enterprise edition, subscriptions and licenses, purchase location, AI developer-tool settings and current console visibility.
The entry does not confirm completed tenant-by-tenant rollout or promise simultaneous access for every region, tool and existing subscription. If the console lacks an entry, do not convert public eligibility into a claim of account activation. Preserve pages and times, and verify with Cloud Billing or Gemini Enterprise administrators or Google Cloud support.
Old conditions remain in linked documentation: preserve the conflict
This review found that the updated release note explicitly removes the email restriction while some linked quota and overview documentation retains the old requirement for the same email subject. That is documentation lag or a public inconsistency. It neither cancels the new release note nor proves every console has caught up.
Preserve the release note, linked-document URLs, capture or screenshot times, project-console results and support-ticket number. If the console still requires the email or rejects a subscription, stop purchases and permission expansion and ask Google to confirm the project's actual eligibility. Do not repeatedly create projects, switch billing accounts or change networks to try your luck.
Check PAYG, Standard, Plus and tool scope separately
The current AI developer-tool settings documentation lists supported editions including Gemini Enterprise Standard, Plus, Standard Emerging Market and Pay-as-you-go, requiring an invoiced Cloud Billing account that receives valid monthly invoices. Standard Emerging Market retains its own eligibility boundaries; September 10 did not remove them.
Developer tools include Antigravity 2.0, Antigravity CLI, Antigravity for IDEs and Android Studio. Newly purchased supported subscriptions may enable them by default in supported purchase locations; existing subscriptions generally require an administrator to enable AI developer tools per location. One working surface does not prove every IDE, region or user has access.
Permissions and security: enabling APIs does not grant user access
Enabling AI developer tools in the console may automatically enable required APIs, but Google explicitly says API activation alone does not grant user access. Users still need appropriate Gemini Enterprise licenses and IAM. Default Gemini Enterprise Administrator or User roles contain relevant permissions; custom roles can narrow access.
Use one nonproduction project and a least-privilege test user to check tool access, file access, terminal commands, security and compliance settings, available models and audit logs. Do not make everyone an administrator merely to reveal an entry point. Check third-party identity providers, locations and tool-specific restrictions individually against current documentation.
Cost validation: no feature quota limit does not mean free
Pay-as-you-go bills actual project feature usage rather than using seat-based pooled feature quotas. AI developer-tool usage for Antigravity, IDEs and Android Studio appears on bills at current Agent Platform prices or corresponding SKUs. Storage, data indexing, Agent Platform and app usage may also be billed separately. Current pricing pages and billing accounts determine rates, currencies, support fees and taxes.
Before release, set a finance-approved low monthly spend limit and budget alerts, run only one small disposable task, and record user, tool, location, time, token or call metrics and cost. Usage & Spending requires relevant Gemini Enterprise and Billing viewing permissions. Check IAM if the page is absent; unread charges must not be recorded as zero.
Stop, rollback and network boundaries
If release-note eligibility conflicts with the console, valid invoices cannot be demonstrated, an edition or location is unsupported, licenses or IAM are unclear, costs are invisible, or models or tools exceed approval, stop activation and disable the pilot switch. Revoke test-user access, retain the existing IDE and manual development workflow, and wait for support confirmation before purchasing or expanding.
For 403, check billing, subscriptions, licenses, location and IAM first. For Usage limit or cost issues, check edition, spending caps and bills. Only use the systematic proxy connection checklist with DNS, TLS, proxy 407 or connection-timeout evidence. A fixed exit cannot remove other eligibility requirements, grant licenses, finish rollout or change prices. PRODUCT_FIT=PARTIAL.
Sources
Frequently Asked Questions
Which restriction was removed on September 10?
The release note explicitly removes the requirement that only recipients of a specified August 17 billing email could access AI developer tools. It extends PAYG subscription and developer-tool eligibility to all projects linked to invoiced Cloud Billing accounts.
Will tools appear automatically after linking an invoiced account?
Not guaranteed. Projects still need subscriptions, licenses, supported locations, administrator configuration and IAM. Existing subscriptions may need per-location activation; account-level rollout completion is not confirmed.
Why do old documents still require the email?
Some linked documents retain old notes while the updated September 10 release note explicitly removes the restriction. Preserve the conflicting evidence and verify actual account status through the console or support.
Which surfaces are included in AI developer tools?
Current official material includes Antigravity 2.0, Antigravity CLI, Antigravity for IDEs and Android Studio. Check each edition, region and organization's availability individually.
Does PAYG having no feature quota limit mean it is free?
No. PAYG bills actual usage. Developer tools, Agent Platform, storage and indexing may appear under different SKUs. Set a low spending cap and verify real bills.
Can a fixed IP make PAYG or developer tools appear?
No. Google controls billing type, subscriptions, licenses, regions, IAM and rollout. A fixed exit has diagnostic value only for DNS, TLS, 407 or connection timeouts.