AI Coding Tool Pricing Tracker

What does AI Coding Tool Pricing Tracker do?

AI Coding Tool Pricing Tracker scrapes the current monthly pricing of every major AI coding assistant — Cursor, Claude Code, GitHub Copilot, Aider, Continue, and Sourcegraph Cody — and emits a single normalized dataset with every tier, every monthly cost, and every advertised feature. Instead of opening seven pricing pages and copying numbers into a spreadsheet, you run this Actor and get a ready-to-compare JSON / CSV / Excel table.

Run it once for a one-shot snapshot, or schedule it daily on the Apify platform to build a pricing history and detect changes the moment a vendor adjusts their plans.

This Actor is part of Ian Mu's 100-Apify-Actor portfolio for the AI / Claude tooling ecosystem (github.com/ianymu) and pairs naturally with claude-verify-before-stop — a Claude Code hook that prevents Claude from declaring tasks done before verifying real output. Both projects share the same philosophy: trust the underlying data source, not the AI's summary.

Why use AI Coding Tool Pricing Tracker?

• Enterprise procurement — When your team is choosing between Copilot Business ($19/user/mo) and Cursor Business, you want exact, dated pricing — not a six-month-old blog post.
• Journalists & analysts — Side-by-side comparison tables ready to drop into an article. Cite the scrapedAt timestamp for credibility.
• Individual developers — Decide whether Aider + your own Claude API key beats a $20/mo Cursor Pro subscription.
• Change detection — Run the Actor on a schedule, diff outputs day-over-day, and get notified the moment Cursor raises Pro from $20 to $25 or GitHub launches a new tier.
• Procurement-friendly format — JSON / CSV / Excel export, ready for Sheets, Notion, Airtable, or your TCO model.

How to use AI Coding Tool Pricing Tracker

1. Open the Actor in Apify Console and click the Try Actor button.
2. (Optional) Edit the Tools to track list if you only care about a subset. Default is all seven.
3. (Optional) Set Currency label — defaults to USD because that's what vendors quote.
4. Click Start. The run typically completes in well under a minute.
5. Open the Output tab and download as CSV, JSON, or Excel, or hit the Dataset API endpoint to integrate with your own pipeline.

Input

Two simple fields, both optional with smart defaults:

Field	Type	Default	Description
toolsToTrack	array of strings	all 7	Which tools to scrape: cursor, claude-code, github-copilot, aider, continue, cody
currency	string enum	USD	Label attached to extracted prices (numeric values come from the vendor page as-is)

Example input:

{
    "toolsToTrack": ["cursor", "claude-code", "github-copilot"],
    "currency": "USD"
}

Output

Each tool produces one row in the dataset. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Example output row:

{
    "tool": "cursor",
    "toolName": "Cursor",
    "scrapedAt": "2026-05-21T03:14:00.000Z",
    "url": "https://www.cursor.com/pricing",
    "currency": "USD",
    "tierCount": 3,
    "tiers": [
        { "name": "Hobby", "priceMonthly": 0, "features": ["Limited completions", "Limited slow requests"] },
        { "name": "Pro", "priceMonthly": 20, "features": ["Unlimited completions", "500 fast requests / mo"] },
        { "name": "Business", "priceMonthly": 40, "features": ["Privacy mode enforced", "Centralized billing", "SSO"] }
    ]
}

A human-readable Markdown summary is also written to the key-value store as pricing-report.md.

Data table

Field	Type	Description
tool	string	Internal slug (e.g. cursor)
toolName	string	Display name (e.g. Cursor)
scrapedAt	ISO date	When this snapshot was captured
url	URL	Source pricing page
currency	string	USD / EUR / GBP label
tiers	array of objects	One entry per pricing tier
tiers[].name	string	Free, Pro, Business, Enterprise, etc.
tiers[].priceMonthly	number | null	Monthly cost; null = "contact sales"
tiers[].features	array of strings	Bullet points scraped from that tier's card
tierCount	integer	Number of tiers captured

Pricing / Cost estimation

This Actor is extremely cheap to run: a full snapshot of all 7 tools makes ~7 HTTP requests with no browser, no proxy, no JavaScript rendering. On Apify's free tier you can run it many times per day without burning meaningful compute units. Recommended cadence: daily or weekly for trend tracking.

How much does it cost to scrape AI coding tool pricing pages? Effectively a fraction of a cent per run.

Tips or advanced options

• Daily change detection — Schedule the Actor to run every morning via Apify's scheduler. Compare today's dataset to yesterday's with a quick diff to spot price hikes the same day they go live.
• Subset tracking — Pass only the tools you care about in toolsToTrack to speed up runs further (although the full run is already < 1 min).
• Graceful failure — If a vendor changes their pricing page layout, that tool is logged as a no_tiers_extracted failure and the rest of the run still completes. Open an issue on the GitHub repo and the per-tool selector will be patched.
• Integrate downstream — Combine with Apify's webhook integrations to push pricing-change alerts to Slack, Telegram, or your data warehouse.

FAQ, disclaimers, and support

Is this legal? Scraping publicly-listed pricing pages for personal/business research is well within standard practice. The Actor uses a clearly-labeled User-Agent, makes only ~1 request per second per vendor, and only retrieves the same HTML a regular browser would. No login is required.

What if a vendor changes their pricing layout? Each tool has its own dedicated parser. If a layout shift breaks one parser, the rest of the run still completes — the failed tool surfaces as a no_tiers_extracted entry in the logs. Please open an issue at the GitHub repo so the parser can be updated.

Will you add tool X? Yes — open an issue at github.com/ianymu (or DM Ian Mu) with the pricing URL and we'll add it. The actor uses one parser per tool, so contributions are easy.

Custom version? Need this wired into your procurement / FinOps stack with Slack alerts and historical diffs? Open an issue and we can build a custom Actor on top.

Built by Ian Mu as part of his 100-Apify-Actor AI tooling portfolio. See also: claude-verify-before-stop — a Claude Code hook that enforces real verification before tasks are marked complete.