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 — the conversational agent, the business case, sprint planning, guided interviews, blueprint narration, and manual model selection. If any of those matter to you, Pro is the entry point.

⚠️ Known gap: Financial analysis has no plan gate at all — unlike the business case sitting next to it, the financial model runs on every plan, Free included. That's current behaviour rather than a promise: it may be brought in line with the business case later, so don't build a workflow that depends on getting it for free.

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.

⚠️ Watch out: There is no automatic fallback to auto models when premium tokens run out. A generation that needs a premium model is refused before it starts, with "You've used your premium-model token allowance for this cycle." On Pro and above you can re-run it on a standard model using the model selector in the Generate dropdown; on Free and Starter that selector is hidden, so wait for the next cycle or upgrade. Generations that run on auto models are unaffected.

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.

Your own agent doesn't spend your budget

The token budget only meters VibeMap's generations. If you instead author your spec with your own connected agent over MCP — your IDE agent writing personas, features, stories, criteria, pages, and schema straight into the project — that work runs on your agent's tokens, and VibeMap only stores the result. It never draws down your VibeMap budget.

💡 The rule in one line: You're only billed when VibeMap generates. Anything your own agent authors is free.

MCP and the REST API are two front doors onto one surface, sharing one auth model — a vm_ personal access token — and that surface is open on every plan, including Free. What varies isn't access, it's capability: each entity keeps its own plan gate, so authoring pages or schema over MCP still needs Starter, exactly as it does in the browser. So on any plan you can stretch a budget much further by having your own agent do the heavy authoring and reserving your VibeMap tokens for the steps you'd rather VibeMap run.

Figure: Billing page.

Managing your subscription

Billing is its own top-level page, not a section of Account. Reach it from your profile menu → Billing, or from the Billing group in the left sidebar, which has four sections: Usage & Analytics, Plans & Pricing, Billing History, and Subscriptions.

• Plans & Pricing — compare tiers and pick a new one. Choosing a plan hands you to Stripe Checkout; your current plan is marked Current Plan.
• Subscriptions — see your current plan and renewal date, open the Stripe customer portal with Manage in Stripe, or Cancel Subscription. Cancelling schedules the end of the current period — the page then shows "Cancellation scheduled" with the date access stops.
• Billing History — invoices, totals, and PDF downloads.

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

Billing → Usage & Analytics shows tokens used this period against your allowance, the premium/auto split, days remaining in the cycle, any overage, and a record-by-record table you can read by generation type and model. 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 Account → Developer. (Keys live under Developer — there is no "API Keys" section of Account.)
2. Under Create New Key, give it a descriptive name — "Claude Desktop", "CI" — and click Generate Key.
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, or let Account → MCP assemble the config for you. See Connect your IDE for the full setup.

Figure: The API keys section of account settings.

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 → Developer, click the delete icon in that key's Action column, then generate a replacement and update your config. The old key stops authenticating immediately.

Account settings

Account has exactly six sections, listed down the left sidebar:

• Profile — display name, username, and profile picture. Your email is shown here but is read-only — it's the address you signed in with.
• Credentials — change your password, plus the Privacy & Data controls: Export downloads a JSON copy of your profile, projects, and billing history (a GDPR-style export), and Delete account removes everything permanently.
• Notifications — which emails VibeMap sends you: product updates, marketing and tips, usage and billing alerts. Security alerts are always on and can't be switched off. (The light/dark toggle isn't here — it's in the profile menu at the bottom of the sidebar.)
• Connections — link GitHub (push generated code, open pull requests) and Vercel (one-click deploy) over OAuth, so VibeMap can build and deploy on your behalf. Connect and Disconnect both live here.
• Developer — your API keys, covered above.
• MCP — a per-IDE setup wizard. Pick Claude Desktop, Cursor, or Windsurf, pick which key the config should reference, and copy the ready-made JSON. Above it, IDE Connection Status lists your keys and when each was last used, which is the quickest way to tell whether your IDE actually connected.

⚠️ Watch out: The MCP wizard never prints your full token — the config it hands you carries a placeholder you swap for the key you copied at generation time. If you no longer have it, generate a new key.

⚠️ Watch out: Manual model selection is Pro and above (Pro, Team, and Enterprise). On Free and Starter the selector is hidden and VibeMap picks the model for each step automatically. What Enterprise adds isn't the selector itself but the list you choose from: Claude 4 Opus is Enterprise-only, and Claude 4 Sonnet unlocks at Team.

⚡ 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.