docs(monitor): document free unchanged pages and unchangedPagesFree - #1308
Open
rakshith48 wants to merge 1 commit into
Open
docs(monitor): document free unchanged pages and unchangedPagesFree#1308rakshith48 wants to merge 1 commit into
rakshith48 wants to merge 1 commit into
Conversation
Monitor checks stop billing pages whose content did not change, on schedules at or slower than the team's plan threshold (firecrawl/firecrawl#4345). - Add `unchangedPagesFree` to the Monitor schema in the v2 OpenAPI spec and to the create-response snippet. - Add an "Unchanged pages" section under Pricing with the per-plan thresholds, and note that the flag re-resolves on schedule or plan changes rather than being fixed at create time. - Correct two statements that are no longer true: the note claiming every check always charges for its scrapes, and the check-detail paragraph describing how `actualCredits` settles. English only; locadex backfills the translations. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs for firecrawl/firecrawl#4345, which stops billing monitor pages whose content did not change on schedules at or slower than the team's plan threshold.
Changes
api-reference/v2-openapi.json—unchangedPagesFree(boolean) added to theMonitorschema, so it appears on create/get/list/update in the API reference.snippets/v2/monitor/create/output.mdx— field added to the example create response.features/monitoring.mdxsamepage costs, the per-plan threshold table, and the fact that the flag re-resolves from the monitor's current schedule and plan rather than being fixed at create time (so an existing monitor starts saving as soon as it qualifies — no recreate needed).actualCreditssettles.estimatedCreditscan far exceedactualCredits.English only —
locadexbackfills translations, matching how recent feature docs have landed.Please confirm before merging
The per-plan table documents Free → daily, Hobby/Standard → hourly, Growth → 15 min, Scale/Enterprise → 5 min. Those are the thresholds from the API PR's rollout plan. The actual values now live in the Autumn
MONITOR_UNCHANGED_MIN_THRESHOLDgrants, which I can't read from here — if the configured grants differ, this table needs to match them, since it's a public pricing promise.Also worth noting: teams with no grant fall back to the API's config default (currently 15 minutes), which the table doesn't describe. That's fine if every product carries a grant, which the API PR says is now the case.
🤖 Generated with Claude Code