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
- October 6 replaces five paid usage tiers with Build, Launch and Grow, automatically upgraded by cumulative organization credit purchases.
- Purchase thresholds are $5/$100/$500, with monthly usage ceilings $500/$5,000/$200,000. Ceilings are not gifted credits.
- Tier, model rate limits and organization/project hard budgets apply separately; one limit number cannot explain every request.
- Use error.code for 429: depleted balance, platform ceiling, organization/project budget and transient rate limits need different handling.
Buying $5 gives a higher ceiling
The October 6, 2026 changelog simplifies five paid tiers to Build, Launch and Grow, automatically upgrading organizations at cumulative purchase thresholds. Exact activation time is not provided.
Credits are balance used to pay for API calls. Higher tiers permit higher monthly usage and typically model throughput; dollar ceilings neither become free balance nor waive charges.
Hypothetical example: an organization buys $5 cumulatively and reaches Build. Its $500 monthly ceiling cannot fund $500 of free tasks; check remaining balance and rates before planning work.
How tier upgrades work
Build requires $5 cumulative purchases and allows $500 monthly; Launch $100/$5,000; Grow $500/$200,000. These are the current docs' US-dollar figures.
Qualification is cumulative organization purchases, not current balance or repeating that purchase each month. Free is separately listed with supported-region conditions; its $100 monthly ceiling is also not a universal gift.
Check actual Usage Tiers under Settings > Organization > Limits after upgrading. A recharge notice does not prove this organization transitioned. No full old-to-new mapping or universal activation delay is supplied.
Monthly capacity does not remove rate limits
Monthly limits govern cumulative cost; rate limits govern requests/tokens per time. RPM is requests and TPM tokens per minute. Bursts can exceed rates long before a monthly ceiling.
Rates apply at organization/project and depend on model/shared limits. Current Standard Build entries for Astra, Sol and Terra show 5,000 RPM and 1,000,000 TPM, not every model, endpoint or mode.
Standard and Ultrafast differ. Inspect the actual model in Limits > Rate limits and queue using returned remaining/reset values. Another key does not grant the same organization a fresh quota.
Your own budgets can block funded requests
Approved monthly usage and administrator spend limits differ. Spend alerts notify while traffic continues; enforced hard budgets return 429 when reached. One stopped project does not prove organization balance is empty.
For organization budgets inspect Organization limits > Spend > Monthly spend limit and Enforce a hard limit. For a project open its Settings > Limits > Spend. Appropriate administrative permission is required.
Organization hard budgets affect all projects; project budgets affect their requests only. Confirm cost and owner-approved budgets before changing them. Propagation is not instant and recorded spend may slightly exceed the setting, so it is not a perfect real-time payment barrier.
Read error.code after a top-up
HTTP 429 or insufficient_quota alone cannot distinguish causes. Retain error category and request time without exposing API keys in logs/support.
credit_balance_exhausted means depleted prepaid balance: check billing and replenish. organization_usage_limit_exceeded means the platform monthly ceiling: seek a higher approved limit; more balance does not replace approval.
organization_spend_limit_exceeded and project_spend_limit_exceeded identify respective hard budgets. Confirm usage, have authorized owners adjust the right limit or wait for the monthly reset. Do not remove organization-wide controls to recover one project.
For actual request/token rate errors, reduce concurrency, respect Retry-After and use bounded retries. Repeated calls resolve neither balance nor budgets and confuse diagnosis.
Identify the missing limit before expanding
Small teams should check organization tier/model rates, balance, then organization/project budgets. All must support larger batches; the Grow figure alone cannot estimate tasks available.
For throughput seek actual model capacity or queue; for monthly usage inspect Upgrade tier. If business budget is insufficient, reduce unnecessary tasks instead of treating tier upgrades as lower prices.
These are public-doc conclusions, with no paid API calls or account verification. Actual organization eligibility, limits and activation remain its own Limits/billing records.
Sources
Frequently Asked Questions
How do old Tiers 1–5 map?
The announcement gives simplification and new thresholds, not a complete one-to-one mapping. Inspect current Limits instead of inferring rates or ceilings from an old number.
Can multiple projects multiply monthly capacity?
No. Tier and approved monthly ceiling belong to the organization, while projects have rates and budgets. Organizational separation does not multiply that ceiling.