Hosted Monitoring

Know when a page, endpoint, or screen stops being right.

Check endpoints, pages, and rendered states before a broken flow reaches users.

Start with direct checks whenever exact status or text is enough. Use AI-reviewed HTML or image checks only when the failure condition is easier to describe than to encode.

Modes

Choose the simplest mode that can prove the state you care about.

Mode What it checks Credits / check Good for
HTTP Status code, headers, and lightweight body assertions. 1 Health checks, API endpoints, simple uptime.
HTML Fetched HTML and exact text or structural assertions. 3 Pages, forms, copy drift, DOM-dependent states.
AI HTML AI evaluation of fetched page content against a natural-language expectation. 30 Messy states that are hard to describe with one selector or substring.
AI Image AI evaluation of a rendered screenshot against a visual expectation. 100 Visual regressions, rendered states, image-based validation.

Pricing

Every watch starts with a request.

The request tells you whether to start the first paid watch, add monthly credits, or top up one-time credits. Faster intervals and more complex checks consume more.

Start Hosted Watch

$39 one-time

  • one workspace
  • one API key
  • first active watch included
  • first 100,000 standard credits included
  • best when this is the first paid watch on the account

Use this when the request response points to a first paid watch instead of credits alone.

Monthly Watch Credits

$9 / month per 100,000 credits

  • recurring monthly credits for ongoing watches
  • adjust quantity at checkout to match expected burn
  • best for watches that should not expire

One-time Check Credits

$9 per 100,000 credits

  • used when you want manual top-ups instead of a subscription
  • works across all modes
  • good for burst traffic and temporary coverage

Estimator

See the expected burn before you request anything.

Checks / month
43,200
Credits / month
43,200
Estimated monthly spend
$3.89
Suggested start
Start Hosted Watch
Suggested monthly credits
1 x 100,000 credits / month

The start pack includes the first 100,000 standard credits. Add monthly credits when the watch should keep renewing automatically.

How It Works

Request, fund, activate.

01

Request

Submit the target, interval, mode, success criteria, and callback destination.

02

Fund

Add the start pack, monthly credits, or one-time credits that match the expected burn.

03

Run

The watch starts once the required balance is in place and can send callbacks when a state fails.

FAQ

What buyers usually want to know first.

Do I need an account before I request a watch?

No. The request comes first. If activation needs payment, the next step is returned immediately.

How do I stop watches from expiring?

Start Monthly Watch Credits at the quantity that matches the estimated monthly burn. That keeps credits replenishing automatically.

When should I use AI checks?

Use direct HTTP or HTML checks whenever possible. Use AI modes when the expected state is easier to describe than to encode.

Can I choose any interval?

Yes. Faster intervals simply consume more credits, and AI-heavy modes become expensive quickly.

How do payments work?

Stripe handles checkout. The first request can return the API key immediately, and payment or top-up enables the watch itself.

For Agents

Request the watch, keep the key, inspect the account.

curl -X POST "https://actobase.com/watch/api/start" \
  -H "Content-Type: application/json" \
  -d '{"target_url":"https://example.com","mode":"http","interval_seconds":60}'

curl "https://actobase.com/watch/api/account" \
  -H "Authorization: Bearer ACTOBASE_API_KEY"