Plans & limits

The app is free, and every plan sees the same data sources — the full options snapshot, the screener, SQL, and all 157 FMP endpoints. The ladder differs on three things only: how many requests you can make per hour, whether you get a personal API key for use outside the app, and historical options bars.

Live prices and limits come from the pricing page; this table reflects the current catalog.

How the hourly limit works

• Every data request — chains, screens, SQL, FMP, historical bars, MCP tool calls — counts against one hourly budget.
• The counter is per user, not per key: creating more API keys doesn’t add quota.
• The window resets on the hour. Hitting the cap returns 429; in the app you’ll see a limit notice with an upgrade link.
• Plan-feature checks happen before the limiter, so a 402 never costs you a request.

What a request buys

These aren’t per-row limits — one request can be an entire chain (every contract on SPY), a 500-row screen, or a 10,000-row SQL aggregation. Well-built apps typically spend a handful of requests per refresh, so even Free’s 20/hour is enough to try real tools; Go suits active building; Research is sized for scanners, dashboards on refresh timers, and programmatic use.

AI credits are separate

CVForge AI credits are a prepaid balance, not a plan feature — every tier can buy and spend them, and your own coding agents (Claude Code, Codex, OpenCode) never touch them.

Managing your plan

• Upgrade, change billing interval, or cancel from the account page (Stripe checkout and billing portal).
• Cancelling keeps the paid plan until the end of the billing period, then falls back to Free — your apps keep working, just at the Free request rate.
• API keys are created and revoked on the account page too; keys are shown once at creation.