Account and billing

Everything tied to your VibeMap account — plans, token budget, usage, API keys, and profile settings. · Optional

You don't need to read this to use VibeMap. Come here when you want to change your plan, understand what your budget covers, issue an API key for your AI coding agent, or manage your profile and data.

Subscription plans

VibeMap combines a subscription with a monthly token budget. Higher tiers unlock more of the pipeline and add heavier, reasoning-grade steps. Every step of the four-phase journey — Research, Plan, Prepare, Develop — is gated by the plan tiers below.

💡 Tip: Several signature features are Pro and above — agent chat, the business case, sprint planning, guided interviews, and blueprint narration. If any of those matter to you, Pro is the entry point.

For the live tier list and full feature comparison, see vibemap.ai/pricing.

Free-plan caps

The Free plan additionally caps generations at 75 per rolling 5-day window. On every paid plan there is no separate generation-count cap — your token budget is the only limit.

Auto vs premium tokens

VibeMap routes routine steps (summary, features, user stories) through fast economy models (auto tokens) and reasoning-heavy steps (schema, pseudocode, business case) through frontier models (premium tokens). Your budget tracks the two pools separately.

💡 Tip: When premium tokens run out, VibeMap gracefully falls back to auto models rather than blocking you — you never get stuck mid-project.

Budgets meter in rolling 5-day windows within the billing period (use-it-or-lose-it), so heavy days don't drain the whole month at once.

Managing your subscription

1. Click your profile avatar in the top-right corner.
2. Select Account, then the Billing section.
3. From here you can:
   • Upgrade or downgrade — changes take effect immediately, with prorated billing.
   • View your current plan and renewal date.
   • Cancel — access continues until the end of the current billing period.

Payments run through Stripe; card details are handled entirely by Stripe and never stored on VibeMap servers.

⚠️ Watch out: Team and Enterprise plans are billed separately from any personal subscription, on the team's own settings page — not here. See Managing your team.

Viewing usage

The Usage section shows generations and tokens used this period against your allowance, a breakdown by generation type, and history across previous periods. If you approach your allowance, VibeMap warns you in the project editor so you can plan ahead.

API keys

API keys are Personal Access Tokens (prefixed vm_) that let your AI coding agent and your scripts authenticate with VibeMap. Most people only need one — for their primary IDE.

Generating a key

1. Open your profile avatar → Account → the API Keys section.
2. Click Generate New Key, give it a name, and optionally set an expiry.
3. Copy the key now — it is shown only once and can't be viewed again after you close the dialog.
4. Paste it into your IDE's MCP config. See Connect your IDE for the full setup.

An account-generated key gives your agent full access to your VibeMap data, so treat it like a password. Behind the scenes, the build-tracking flow also uses narrower agent and ci_review scopes (an agent can claim and submit acceptance criteria but can't resolve its own review; a CI token can resolve reviews) — see the developer docs for that lower-level model.

Revoking a key

If a key is exposed (committed to git, leaked in a screenshot, lost to a former teammate), open Account → API Keys, click Revoke next to it, then generate a replacement and update your config. Revocations take effect within seconds.

Account settings

• Profile — display name, email (verification required for a new address), profile picture, and password.
• Preferences — notification preferences and light/dark theme.
• Data export — download a portable JSON bundle of everything the platform holds about you (a GDPR-style export), from the privacy section of your account.

⚠️ Watch out: Manual model selection is Enterprise-only. On every other plan VibeMap picks the best model for each step automatically — you don't need to choose.

⚡ Power-user hints

• One key per surface. Issue separate keys for your IDE, CI, and side projects so you can revoke one without disrupting the others.
• The spec is a live source, not a ZIP. There's no "export project as ZIP" button — instead your features, personas, stories, ACs, pages, and schema are always readable via the REST API and MCP server, so your agent and tools (Linear, Notion, custom scripts) pull straight from the source of truth.
• Out of budget mid-project? Existing project data stays fully editable and your IDE agent can keep working through already-generated acceptance criteria — only new AI generations pause until the next window or an upgrade.

↔ The traditional way

Without VibeMap you'd juggle several tools and bills: a PM suite, a diagramming tool, an issue tracker, plus per-seat AI subscriptions for everyone. VibeMap folds the whole spec-to-handoff pipeline into one subscription and one metered budget, and — on Team plans — one shared bill instead of a subscription per person.

What's next

• Team workspaces overview → — share projects and billing across a group.
• Connect your IDE → — put your new API key to work.