How often does Wachete check a website for changes?

Wachete says it can check a website as often as every few minutes on a paid plan, or as infrequently as once a day on the free plan. You choose a monitoring frequency when you create a monitor, and the available cadence depends on your plan. Wachete’s published general range does not establish an exact interval for every named tier, so check the current setting available to your account before relying on a specific schedule.

What “every few minutes to once a day” means

Wachete describes its configurable monitoring range as “Anything from every few minutes to once a day.” That is the clearest published answer to how often it checks. It is a service-level range, not a promise that every plan or every monitor can use every interval. Wachete’s uptime-monitoring page also says paid-plan outage notifications arrive within minutes, as often as the page is checked.

When setting up a monitor, select the frequency offered for that monitor and plan. More frequent checks can detect a change sooner, while a less frequent schedule may be sufficient for pages that change slowly. Check the current plan details in your Wachete account: the public plan information reviewed for this article did not provide readable, reliable intervals for each named tier.

How to choose a monitoring frequency

1. Decide how quickly you need to notice a change. A time-sensitive outage or content change may call for a shorter interval than a page that is updated only occasionally.
2. Check the cadence your plan makes available. Wachete’s general range is not a tier-by-tier schedule. Use the interval shown when creating or editing the monitor.
3. Consider what counts as a useful alert. Frequent checks can surface changes sooner, but alert delivery follows detection; a check interval is not a guarantee of end-to-end notification time.
4. Review the monitor after setup. Confirm its selected frequency and notification destinations, especially if the page or the urgency of monitoring changes.

Wachete says it does not impose a monthly check budget and that pages are checked at the interval chosen for the plan. This is Wachete’s own product statement; verify current account and plan details if the monitoring volume matters to your use case. Wachete’s FAQ says monitoring runs on its servers, so your computer or phone does not need to stay online.

Using the Wachete API recurrence value

Wachete’s REST API documentation represents a monitor’s recurrence with a recurrenceInSeconds parameter. Its example uses 86400, which is 24 hours. This illustrates the parameter’s unit and an example value; it does not establish that arbitrary intervals are available to every account or through every interface. Consult the Wachete API documentation for the endpoint, authentication, and request structure applicable to your integration.

86400 seconds = 24 hours = one day

Do not infer a named plan’s minimum interval from the API example. The available recurrence is still subject to Wachete’s plan and current product settings.

Check cadence, detection, and notification are different

A configured interval describes how often Wachete checks. The time until you receive an alert can also depend on when a change occurs relative to a check and on notification delivery. For example, a change just after a check may wait until the next scheduled check to be detected. Wachete says paid-plan outage notifications arrive within minutes, as often as the page is checked, but that statement should not be read as a guarantee that every change produces an instant alert.

Common questions and troubleshooting

Why can’t I select a check every few minutes?

The general published range spans from every few minutes to once a day, but the available cadence depends on the plan and monitor settings. Check the options shown for your account and its current plan details. Do not assume that every tier supports the shortest interval.

Does “every few minutes” mean I will always be notified within a few minutes?

No. Check frequency, change detection, and alert delivery are separate stages. Wachete describes paid-plan outage notifications as arriving within minutes, as often as the page is checked; this is not an instant-delivery guarantee for every kind of change.

Does my computer need to stay on?

No. Wachete says monitoring runs on its servers, so your computer or phone does not have to remain connected. See its FAQ.

What does recurrenceInSeconds: 86400 represent?

The API example represents a recurrence of 86,400 seconds, or one day. It is an example, not evidence that every interval can be configured on every plan. Refer to the API documentation for the request details.

Where can I find the exact interval for my tier?

Review the frequency selector for the monitor and the current plan information in your account. Wachete’s public material establishes a general range, but the plan table reviewed here did not expose readable intervals for each named tier.

When a screenshot helps—and when it does not

Wachete is the service in this article for scheduled website-change monitoring. A screenshot API serves a different purpose: capturing a page as an image or PDF on request. It does not replace a change monitor or independently tell you when a page changed. If your workflow also needs clean visual captures for reports, archives, or review, ScreenshotNeo is the screenshot API alternative to try first: it removes known consent banners, newsletter popups, and chat widgets before capture, and only clean shots are billed.

Or skip the browser setup

ScreenshotNeo takes a screenshot with one GET request. See the ScreenshotNeo API documentation for options and response details.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

• Cookie banners, popups, and chat widgets are removed before the shot; each cleanup step can be turned off.
• Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed. Response headers identify the page verdict and billing status.
• An MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs.
• The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.

Sign up free for 1,000 screenshots a month, with no card required.

Sources

• Wachete: Website Uptime & Availability Monitoring
• Wachete FAQ
• Wachete REST API documentation