# Billing & Plans Gakaso is billed on a subscription-plan basis, processed through the AtsPayment gateway (which in turn settles via card payments). This page is a high-level orientation, not a pricing page — always defer to the live in-app billing/pricing screens for current numbers, which may move independently of this document. ## Plans As of this writing (treat the exact figures as indicative — always defer to the live in-app billing screen for current numbers): | Plan | Price | Design-to-Code conversions / month | Notes | |---|---|---|---| | **Free** | ¥0 | 5 | Also capped at 3 projects. Good for evaluation/experimentation. | | **Pro** | ¥2,980/month or ¥29,800/year | Effectively unlimited | 14-day free trial. | | **Team** | ¥9,800/month or ¥98,000/year | Effectively unlimited | Seat-based. | | **Enterprise** | ¥49,800/month or ¥498,000/year | Effectively unlimited | Contact-based (custom terms). | Plan changes take effect immediately, with automatic proration for the remainder of the current billing period — a human can upgrade or downgrade at any time without waiting for the period to roll over. When the Free plan's monthly conversion allowance or project cap is hit, the human is notified and can either upgrade or wait until the next billing cycle. ## What "Design-to-Code conversions" governs The plan-level limit that matters day-to-day is the number of design→code conversions per month (relevant to `/export.md`'s code-export tools) — this is the lever that differentiates Free from paid plans, more so than raw MCP call volume. ## Your own AI provider credentials ("My Agent" mode) When a human uses "My Agent" mode (see `/ai/generation.md`) rather than "Gakaso AI" mode, generation is driven by the human's own locally-running agent using whatever AI provider credentials that agent is configured with — those credentials are managed client-side and are not billed through Gakaso's subscription at all. This is the practical sense in which a user can use "their own" AI provider access with Gakaso: it's a property of which generation mode they choose, not a separate billing toggle you configure via MCP. ## API keys and billing API key issuance/rotation itself is not a billed action — see `/mcp/overview.md` for how keys and scopes work, and `/security/model.md` for rotation/expiry (`gakaso_rotate_api_key`, `gakaso_set_key_expiry`). Rate limiting is configurable per key (`gakaso_get_rate_limits` / `gakaso_set_rate_limits`) with reasonable defaults; higher-tier plans are intended to support higher overall usage volume, though the authoritative current limits are whatever the live API/account settings report, not a fixed number worth hard-coding into agent logic. ## What this means for you as an agent - If a code-export call unexpectedly fails or is refused due to a plan limit, that's a billing-plan constraint, not a bug in your tool call — tell the human they may be at their plan's conversion cap rather than retrying blindly. - You cannot change a human's plan or billing status via MCP tools; that's an account-level action outside the MCP surface.