Competitor monitoring API that tells your code what a competitor just changed.

A competitor monitoring API watches competitor web pages on a schedule and sends your code a structured event when something you defined changes. With Verid you name the page and the fields, for example each plan price and the homepage headline, gate the alert with a rule such as a 5 percent price drop, and every qualifying change arrives as an HMAC-signed JSON webhook carrying the previous value, the new value and the list of fields that moved.

Anything on a public URL. The nine pages worth watching are the pricing page, the plan comparison table, the homepage hero, the changelog or release notes, the docs index, the careers board, the customer wall, campaign landing pages, and the status or trust page. Each becomes one monitor with its own fields, its own rule and its own interval, which is what lets a pricing page run hourly while a careers board runs daily.

Those are competitive intelligence platforms built for product marketing: curated feeds, battlecards, enablement content, win-loss analysis and annual contracts. Verid is the raw signal layer underneath. You get a precise structured change event at a self-serve price and decide what to build on it, and there is no analyst, no battlecard editor and no narrative. Teams that need both usually run Verid as the detection layer and keep the platform for the narrative.

There is a dashboard for managing monitors and reading run history, but it is not where the product happens and you are not expected to live in it. The output is a webhook, so the dashboard your team actually reads is whatever you build on your own data: a Slack channel, a CRM field, a warehouse table, a BI chart. That is a deliberate trade. If a ready-made competitive dashboard is what you want, a platform is the better purchase.

Yes, and it is the most common use. Extract each price as a bare number, either with a CSS selector that lands on the node holding the digits or with a regex that pulls them out of the surrounding sentence, then gate the monitor with a threshold predicate such as field_decreases_by_percent at 5, so currency rounding and cosmetic edits stay silent. The webhook carries the old price, the new price and the field name, which is enough for a repricing service to act without fetching the page again.

Detection lag is your check interval plus the time it takes to fetch and render the page. The interval is set per monitor in seconds and floored by your plan: once a day on Free, every two hours on Lite, hourly on Starter, every fifteen minutes on Pro and every five minutes on Scale. Pricing and campaign pages usually run at the floor while hiring and customer pages run daily or weekly.

Roughly six pages per competitor covers price, packaging, positioning, launches, hiring and proof. Five competitors is therefore about 30 monitors, which fits the $19 Starter plan with room to spare, and twenty five companies six pages deep is 150 monitors, which is Pro at $49. Start with the two pages per competitor that would actually change a decision, then widen.

Three levers, in order of effect. Extract only the fields that carry meaning rather than selecting a whole section. Put a number on the rule, so a price field fires on a 5 percent move rather than any move at all. Set an interval that matches how fast the page really changes. Teams that do all three still read the channel six months later, and teams that do none of them mute it in week three.

Enable visual monitoring on the same monitor and every check also screenshots the page and pixel-diffs it inside the regions you chose, with its own percentage threshold. You get the design change as an image pair and the copy change as named fields, from one check on one URL, which is the pairing that explains both what moved and what it now says. Visual monitors carry their own plan cap, from one on Free to 500 on Scale, because every one of them renders a browser and stores images.

Yes. Deliveries are configured per monitor, so competitor A can post into the revenue channel while competitor B goes to your own endpoint and into the warehouse. One monitor can hold up to 25 endpoints on the Scale plan, one on Free, and the four channel types are signed webhook, Slack, Discord and email.

Only where those live on a stable public page. A paid landing page behind an ad is an ordinary URL and monitors well, so offer copy, promo codes and trial lengths are all in scope. Ad libraries, social feeds and review platforms usually require a login or an API of their own, and a tool built for social listening or review monitoring will serve you better there.

That is the intended shape. Because every change is a signed JSON POST rather than an email, the natural consumers are a handler that writes a warehouse row, a workflow in n8n, Zapier or Make, or an agent that needs to know a competitor price moved without re-reading the whole page. The payload names the changed fields, so a consumer switches on strings instead of comparing documents.

Reading a competitor public web page is ordinary market research, and businesses have done it since long before it was automated. What matters is how you do it: respect robots directives and terms of service, keep the check frequency reasonable, take only what you need, and do not touch anything behind a login you were not given. Verid gives you per-monitor interval control precisely so a monitor can stay polite, and the choice of target remains yours.

Yes, within honest limits. The permanent Free plan gives you five monitors checking once a day, with fourteen days of run history, one delivery endpoint each and no card required. That is one competitor covered five pages deep, or five competitors covered on pricing alone. Faster intervals and higher monitor counts start at $9 a month, and every predicate and extraction method is available on every plan.