Public Changelog & Release Notes Intelligence Agent

Pricing

Rating

Developer

Actor stats

Categories

Share

Turn public changelog and release-notes pages into compact product-update intelligence for AI agents, competitive monitoring, product marketing, developer relations, security review, and sales research.

The Actor fetches the supplied public changelog URLs and extracts release entries with titles, dates, version hints, categories, snippets, matched focus terms, confidence, completeness, diagnostics, and a stable changelog hash for change tracking.

How To Use It

For a first-pass product-update inventory, provide public changelog or release-notes URLs and leave focus terms empty:

{
"changelogUrls":["https://vercel.com/changelog"],
"focusTerms":[],
"previousChangelogRecords":[],
"maxEntries":10,
"requestTimeoutSecs":20
}

For targeted monitoring, add focusTerms such as a product name, API, feature, integration, security term, pricing term, or competitor name. If focus terms are supplied, useful-result charging requires at least one matched term inside the extracted entries.

For repeat monitoring, pass previous dataset records from this Actor in previousChangelogRecords. If the changelog hash is unchanged, the record is written as changeStatus: "unchanged" without the useful event charge.

What It Finds

Useful evidence can include:

• release-note or changelog entry titles, dates, version hints, and snippets
• latest entry date and entry count
• heuristic categories such as added, fixed, security, deprecated, breaking, and improved
• matched focus terms for product, API, integration, security, pricing, or competitor monitoring
• page title, evidence URLs, confidence score, completeness score, diagnostics, and a stable changelog hash

Pricing

Pay-per-event pricing is designed to stay predictable:

• apify-actor-start: a tiny run-start fee
• useful-changelog-result: charged only for useful public changelog or release-note intelligence records
• no apify-default-dataset-item

If focusTerms are supplied, useful-result charging requires at least one matched term inside the extracted entries. Invalid inputs, duplicate equivalent URLs, private-network targets, query/fragment/token inputs, failed fetches, focus misses, unchanged records, and pages without changelog entries do not charge the useful event.

Output

Each page returns one record with fields such as:

• status, changeStatus, inputUrl, finalUrl, and siteOriginUrl
• pageTitle, entries, entryCount, and latestEntryDate
• categories, matchedFocusTerms, changelogHash, and previousChangelogHash
• confidenceScore, completenessScore, missingFields, and diagnostics

Entry categories are heuristic labels such as added, fixed, security, deprecated, breaking, and improved.

Boundaries

This Actor is a changelog and release-notes intelligence tool, not a generic webpage monitor, article extractor, website crawler, GitHub API client, software-vulnerability scanner, pricing monitor, social scraper, or browser renderer.

It fetches only the provided public page URLs. It does not log in, use cookies, render JavaScript, call private APIs, bypass paywalls, scrape search-engine results, or enrich private persons.

Not For

This Actor is not a generic webpage diff monitor, vulnerability scanner, package registry tracker, GitHub API client, pricing-page monitor, social listening tool, browser renderer, or search-engine scraper. It extracts bounded public changelog and release-note evidence for downstream review.