Documentation Deprecation Monitor
Pricing
from $50.00 / 1,000 documentation checks
Documentation Deprecation Monitor
Monitor explicit HTML, Markdown, and OpenAPI documentation for evidence-backed deprecations, removals, authentication changes, migrations, and endpoint revisions.
Pricing
from $50.00 / 1,000 documentation checks
Rating
0.0
(0)
Developer
Flintglade
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
Monitor explicit documentation URLs and report evidence-backed endpoint, authentication, migration, deprecation, sunset, removal, version, and policy changes.
What this does not do
- No generic site crawl or universal breaking-change detection.
- No promise that all breaking changes are documented.
- No code migration, patch generation, or LLM summary.
- No login bypass or private-doc monitoring without user-authorized credentials.
Sources and authorization
Every HTML, Markdown, or OpenAPI document is an explicit user URL passing the SSRF gate. Version 1 uses bounded HTTP only, follows at most five revalidated redirects, accepts only optional Authorization/Accept headers, and performs no recursive discovery.
Input
Submit 1-100 documents with url, type, and optional priorUrl, HTML selectors, or secret headers. A baselineStoreId enables scheduled monitoring.
Output
Each row contains baseline state, canonical hashes, category deltas, exact before/after excerpts and locators, OpenAPI operation changes, severity, source metadata, and diff artifacts. The final run summary is uncharged.
Pricing
documentation-check costs $0.05 per terminal document check. Baseline creation, unchanged/changed reports, and definitive 404/410 results are charged. Blocked/auth/rate/transient/parse failures and missing requested priors are uncharged. Maximum event cost is admitted checks multiplied by $0.05, plus platform usage.
State and partial failures
Explicit priorUrl comparisons are stateless. Persistent baselines are journaled in the selected KVS and committed only after Apify confirms the paid event. A 304 with a valid baseline is a successful unchanged check; uncharged failures never advance state. Duplicate inputs receive explicit uncharged rows.
Resources and data handling
Limits are 256 MB minimum, 1024 MB default, 2048 MB maximum, 600 seconds, 2 MB per response, eight concurrent requests, and 100 documents. Secret header values are never echoed. Delete the run storages and chosen baseline KVS records to remove data.
Rights, attribution, and limitations
Users must be authorized to fetch submitted documentation. The controlled fixture is Flintglade-authored. Historical changelog text is labeled and cannot create a high-severity alert by itself. Provider documentation can be incomplete, and unchanged text cannot prove an API is unchanged.
Support: support@flintglade.com
