Two customer-supplied observations of the same subject, including the values and evidence your system collected.
Competitor pricing change monitoring API
Monitor competitor pricing changes from observations you supply
When your crawler, licensed feed, or internal system records pricing before and after, ChangeGraph turns the difference into a typed event your workflow can route.
Free: 25 monitored entities/month. Developer: $299/month for 250 monitored entities. Compare plans.
Exact use case
A competitor changes a plan price, packaging, or included feature and your team needs a dated, machine-readable record instead of another screenshot.
Typed change events with direction, before and after values, evidence, timestamps, and a confidence score derived from the observation.
Classifies differences in supplied observations and keeps the evidence attached to each resulting event.
After monitor setup, a successful authenticated POST /v1/monitors/{id}/snapshots that evaluates an observation and returns typed changes or a correct no-change result.
Turn a pricing observation into a dated change
When a competitor changes a plan price, your team needs the old value, the new value and the evidence behind the difference. The API classifies pricing observations your crawler, licensed feed or internal system has already collected.
The synthetic example changes plan.pro.monthly from 49 to 59. The resulting pricing event describes the increase. This page does not collect a live competitor price or promise a built-in data feed.
Use the same subject and fact keys in each snapshot
Company-data change detection needs comparable observations. Map each source field to a stable fact key and preserve the subject, source and observation context so the before-and-after values refer to the same thing.
For a pricing field, map your collected plan value to plan.pro.monthly in both snapshots. Keep currency, billing period and source definitions comparable before sending it. A company name or URL alone does not supply these facts.
Read the event type, direction and supporting facts
A useful pricing alert tells the reviewer what changed and where that conclusion came from. The same event structure can describe other supported customer-supplied company signals; your workflow decides which kinds are relevant.
Inspect kind, direction, factKey, before, after and evidence. The returned confidence is derived from the observations; it is not a probability of a future purchase or independently verified source accuracy.
Establish a baseline, then submit the next observation
Create a monitor and retain its returned ID. Submit the initial snapshot as the baseline, then send a later observation for comparison. Your own alert, CRM or research system can consume an accepted event from the response.
The accepted authenticated sequence uses POST /v1/monitors, then POST /v1/monitors/{id}/snapshots. The first snapshot establishes a baseline; the changed sample returns typed events. A correct no-change result is also interpretable. The API does not send a customer alert for you.
OpenAPI-grounded keyless demo
Detect pricing changes
Edit the supplied example, send it to /v1/demo/detect, and inspect the service’s unedited JSON response. The demo stores nothing and consumes no account quota.
Response
Run the demo to see the API response.
A successful response demonstrates the bounded classification or calculation shown here. It is not evidence of a deployed connector, autonomous external action, customer outcome, or commercial performance.
Pricing and recurring use
Choose a plan by monitored entities
Start with one subject from data you already hold. Choose a larger allowance as you add justified monitoring coverage across products or client portfolios. The plan unit is a monitored entity, not an alert count; collection and downstream routing remain yours.
Free
$0/month
25 monitored entities included per month.
Developer
$299/month
250 monitored entities included per month.
Growth
$999/month
1,500 monitored entities included per month.
Scale
$2,499/month
6,000 monitored entities included per month.
Prices in USD, billed monthly. Paid-plan overages and caps apply; see full pricing and Enterprise. The keyless demo requires no account.
Capability boundary
What this page does not promise
ChangeGraph does not crawl websites, acquire proprietary data, or provide a competitor data feed. It only evaluates observations you send.
- The demo qualifies the transformation only; account verification, key creation, and a successful authenticated primary-value request are required for activation.
- Inputs and outputs must be reviewed in the context of your own data rights, policies, and operational controls.
- No ranking, accuracy, savings, recovery, prevention, customer, or revenue result is claimed.
From evaluation to first value
A short, explicit path
- Run the keyless demo.
Confirm that the input and output shape match the job you need done.
- Create and verify a sandbox account.
The email claim flow creates a product-scoped API key. No card is required for the free tier.
- Call the authenticated primary-value operation.
After monitor setup, a successful authenticated POST /v1/monitors/{id}/snapshots that evaluates an observation and returns typed changes or a correct no-change result.