Competitor Monitoring API Pay As You Go: What a Check Costs

You want to watch forty competitor pages. Pricing, changelogs, careers, status, docs. Most of them will not change this quarter — which is exactly why you want them watched, because nobody is going to open a rival's careers page every Monday by hand.

Then you read a monitoring vendor's pricing page and find that the plan which allows forty pages is $70 a month, whether those pages change or not.

A competitor monitoring api pay as you go bills a different unit. Not how many pages you are permitted to have. How many comparisons actually ran.

What is metered, and what is not?

One thing is metered: a target that got fetched and compared. That is 3 credits, the track_changes price, per target per check.

Everything around it is free.

• Management calls cost nothing. Creating, listing, updating, pausing or deleting a monitor is a zero-credit call. There is no per-monitor fee and no per-page fee, and an account holds up to 50 monitors of 20 targets each whether or not you use them.
• Blocked and failed targets are not charged. A check holds 3 credits per target up front and settles to what actually ran, so a Cloudflare wall, a timeout or a 500 costs nothing.
• The estimate is a ceiling. Every monitor reports estimated_credits_per_month, which assumes every target is fetched and compared on every run. Real months come in under it.

What does a check actually cost?

A credit is $0.003 at the one-time 1,000-credit pack rate, so one target compared once is $0.009. Over thirty days:

The third row is the one that reframes the problem. Frequency is what costs money; breadth is nearly free. Watching forty pages once a week is cheaper than watching a single page every hour, and the forty-page watch is the one that catches a competitor quietly opening a New York sales office.

Why does the billing unit change what you monitor?

Because a page cap forces you to decide, in advance, which competitor pages matter — and you have to decide before you know.

Visualping is the clearest example of the other shape, and its pricing page as of 2026-09-09 reads: free gives 150 checks across 5 pages at hourly resolution; Personal 1K is $14 a month for 1,000 checks across 10 pages; Personal 5K is $35 for 20 pages; Business 20K is $140 for 200 pages and 5 seats. Two ceilings and a seat count, and you hit whichever one comes first.

At small scale that is a fine deal, and worth saying plainly: five pages checked daily is 150 checks, which fits inside their free plan. We charge $1.35 for it.

The shapes diverge when breadth outruns frequency. Two hundred pages checked weekly is about 800 checks a month — comfortably inside a $14 plan's check budget, and twenty times over its page budget, so it costs $140. Metered, the same two hundred pages are 2,400 credits, around $7.

What you give up

A per-page subscription is buying a product, not just a meter — a UI with side-by-side visual diffs, Slack and Teams destinations, false-alert tuning, a recorder for clicking through a login before each check. CrawlForge monitors are an API: one POST with a cron schedule, a CSS selector to scope each diff, and delivery by email or signed webhook. How that endpoint works is a different post.

And it reads pages you point it at. It holds no contact records, no firmographics and no org charts, so it sits above whatever database your enrichment already runs on rather than replacing it.

The signup grant is 1,000 credits, which covers a five-page daily watch for two months before you spend anything — and those credits do not expire, so a monitor you pause in July still has its balance in November.

Start free with 1,000 credits, or open the monitors dashboard and read one real check before you write any code.