AI Coding Tools Pricing & Usage Limits dataset (Cursor, Claude Code, Codex, Copilot)

AI Coding Tools Pricing & Usage Limits gives you one clean, structured dataset of the plans, monthly prices and usage limits of the main AI coding tools: Cursor, Claude Code, OpenAI Codex, GitHub Copilot, Windsurf, Google Antigravity, Lovable, Bolt, v0, Replit Agent, base44, JetBrains AI, Zed, Cline, Aider, Continue, CodeRabbit, Qodo, Greptile, Cursor Bugbot and Claude Code Review.

Every row carries its source URLs and last-verified dates. Each run also re-checks the vendor's live pricing page and tells you whether the recorded price is still shown there.

Vendors change AI coding plans constantly: new tiers, weekly caps, credit pools, 5-hour windows. This Actor saves you from reading 20 pricing pages and help-center articles by hand.

What data do you get?

• Plans and prices: monthly USD list price per plan, with billing notes (annual price, per-seat price).
• Usage limits per plan, split into 5-hour or daily, weekly and monthly windows. Each window is labeled as one of:
  • published_amount: the vendor publishes a number, such as 500 requests or 300 credits.
  • relative_multiple: the vendor gives a multiple such as "5x Pro".
  • exists_size_not_published: a cap exists but the vendor doesn't say how big it is.
  • none_published: no cap is published for that window.
  • no_limit: the vendor says there is no limit.
• What happens when you hit the limit: wait for a reset, buy credits, pay overages, or upgrade.
• Tool summary: whether there is a free plan, the entry price, and a one-line summary of all plans.
• Recent pricing changes per tool, with dates and source links.
• Provenance: source URLs with the date each was last verified.
• Live check: the status (confirmed, not_found_on_page, fetch_failed), when the check ran, the USD prices found on the live page, and the matching plan on the page.

Numbers are never estimated. If a vendor doesn't publish a limit, the dataset says so instead of guessing.

Use cases

• Choosing a tool or plan: compare what $20, $100 or $200 a month buys across Cursor, Claude Code, Codex and Copilot.
• Team procurement and budgeting: see per-seat prices and caps before rolling a tool out.
• Comparison sites, newsletters and analysts: keep pricing tables up to date from one feed.
• Apps and AI agents: give your app or LLM agent structured, cited pricing data instead of stale training data.
• Market research: track how AI coding pricing moves over time with scheduled runs.

How to use it

1. Click Start. With the default input you get every tool, both plan rows and tool summaries, and a live re-check.
2. Optional: filter by tools (slugs such as cursor, claude-code, codex, github-copilot) or by category.
3. Download the results as JSON, CSV or Excel, or read them through the Apify API. The Plans & limits and Tool pricing summary views give you ready-made tables.
4. Schedule it weekly to get a fresh live check, and filter on liveCheck.status = not_found_on_page to spot prices that may have moved.

Input

Field	Description
tools	Optional list of tool slugs. Empty means all tools.
categories	Optional: ai_coding_agent_or_editor, ai_app_builder, ai_ui_generator, ai_code_review.
outputMode	plans_and_tools (default), plans_only, or tools_only.
liveCheck	auto (default: HTTP, browser for JavaScript pages), http, browser, or off.
maxConcurrency	Pages checked in parallel (1–10).
proxyConfiguration	Optional Apify Proxy.

{
  "tools": ["cursor", "claude-code", "codex", "github-copilot"],
  "outputMode": "plans_and_tools",
  "liveCheck": "auto"
}

Output example

A plan row (shortened):

{
  "recordType": "plan",
  "toolSlug": "cursor",
  "toolName": "Cursor",
  "category": "ai_coding_agent_or_editor",
  "plan": "Plus",
  "priceUsdMonthly": 8,
  "priceNote": "$8/mo ($80/yr); Cursor models only",
  "limitFiveHourOrDaily": "No 5-hour or daily cap published",
  "limitWeekly": "1x: the base weekly pool (size not published)",
  "limitMonthly": "No monthly cap; pool refreshes weekly",
  "usageLimits": {
    "weekly": { "kind": "relative_multiple", "relativeMultiple": 1, "description": "1x: the base weekly pool (size not published)" }
  },
  "limitUnit": "multiple of Plus's weekly pool",
  "whenYouHitTheLimit": "Wait for the weekly refresh, buy top-ups (or Auto Top-up) at per-model rates, or upgrade for a bigger pool.",
  "sources": [
    { "title": "Pricing page", "url": "https://cursor.com/pricing", "lastVerified": "2026-10-26", "covers": "pricing" },
    { "title": "Cursor docs: Models & Pricing", "url": "https://cursor.com/docs/account/pricing", "lastVerified": "2026-10-20", "covers": "usage_limits" }
  ],
  "pricingLastVerified": "2026-10-26",
  "limitsLastVerified": "2026-10-20",
  "liveCheck": {
    "status": "confirmed",
    "checkedAt": "2026-11-04T15:57:10Z",
    "url": "https://cursor.com/pricing",
    "fetchMethod": "http",
    "expectedPriceUsd": 8,
    "usdPricesFoundOnPage": [0, 8, 30, 100, 200],
    "note": "$8 is shown on the live page",
    "pagePlanMatch": { "plan": "Plus", "price": "$8", "billingPeriod": "month" }
  }
}

A tool row has recordType: "tool" with hasFreePlan, entryPriceUsdMonthly, entryPlanLabel, pricingSummary, recentChanges, the same provenance fields and a liveCheck that lists the plans found on the live page.

How is the data collected and kept fresh?

The dataset is researched from each vendor's own pricing page, docs and help-center articles. Every value is stored with the URL it came from and the date it was checked. New releases of the Actor update the bundled data. On every run, the live check re-loads each vendor's pricing page and compares it with the recorded price, so you can see at a glance whether a row still matches the vendor's page today.

Live check statuses

Status	Meaning
confirmed	The recorded price is shown on the live pricing page.
not_found_on_page	The page loaded but the recorded price wasn't found. The price may have changed, or the page shows it differently (for example annual-only prices, or prices on another page). Review these rows.
fetch_failed	The page could not be loaded during this run.
no_price_to_check	The tool has no flat price to compare, for example usage-based pricing.
skipped	The live check was turned off.

How much does it cost?

Pay-per-event: a small fee per record returned, plus Apify's standard Actor start fee. A full run returns about 50 records and costs about $0.25. Filter by tools to pay for fewer records. You can set a maximum cost per run, and the Actor stops before going over it.

FAQ

Are the usage limits official? Each limit is quoted from the vendor's own pages, linked in sources. Where a vendor only says "limited" or "higher limits", the dataset marks the window exists_size_not_published and never guesses a number.

Why do some rows say not_found_on_page? Some vendors show monthly prices only behind a toggle, list prices on a different page than the one checked, or describe usage-based pricing in docs. The row keeps the verified value from its source and flags it for review, so you never get a silently wrong number.

How often is the data updated? The live check runs every time you run the Actor. The bundled research data is refreshed with new Actor builds, and every row shows its lastVerified date.

Can you add a tool? Yes. Request it in the Issues tab.

Can I use it in my app or with an AI agent? Yes. Call the Actor through the Apify API or the Apify MCP server and read the dataset items as JSON.

Limitations

• Prices are USD list prices. Taxes, regional prices and discounts are not included.
• Enterprise and "contact sales" plans are described in pricingSummary but have no price.
• The live check confirms whether a price is still shown on the vendor page. It does not extract new usage limits, which come from the researched data and its limitsLastVerified date.