Billing for monitors
Per-check credits × schedule frequency, dryRun cost previews, skip-and-retry on low balance, and plan limits.
Monitors bill like the rest of the API — no separate monitor fee.
What's free vs. what bills
- Management is free. Creating, listing, getting, updating, deleting, pausing, and resuming monitors and webhook endpoints costs 0 credits.
- Only the scheduled poll bills, at that operation's normal per-request price — same as calling the route directly. A check against
GET /v1/twitter/profiles/{handle}/tweetscosts whatever that route normally costs. - Empty checks still bill. A check that finds zero new items costs the same as one that finds ten. The upstream provider charges either way.
- Triggers and test sends.
POST /v1/monitors/{id}/triggeris free; the poll it enqueues bills normally.POST /v1/webhook-endpoints/{id}/testsends a synthetic sample and never touches the source — 0 credits. - Shared targets. If multiple customers monitor the same target, each is billed full price. Internally we coalesce the upstream fetch so we only pay the provider once.
The cost math
perCheckCredits is the operation's normal price. checks per day comes from the schedule: a 15-minute interval is 1440 / 15 = 96 checks/day; hourly is 24; 1-minute is 1,440.
| Interval | Checks/day | Example @ 1 credit/check | Example @ 2 credits/check |
|---|---|---|---|
| 1 min | 1,440 | 1,440/day · 43,200/mo | 2,880/day · 86,400/mo |
| 5 min | 288 | 288/day · 8,640/mo | 576/day · 17,280/mo |
| 15 min | 96 | 96/day · 2,880/mo | 192/day · 5,760/mo |
| 1 hour | 24 | 24/day · 720/mo | 48/day · 1,440/mo |
| 6 hours | 4 | 4/day · 120/mo | 8/day · 240/mo |
| 24 hours | 1 | 1/day · 30/mo | 2/day · 60/mo |
Check any operation's credit price on its API reference page before budgeting a schedule.
Preview the cost before you commit
Every monitor create/get/list response includes a live costPreview. Add ?dryRun=true to validate the request and return the preview without creating anything or running a baseline check:
The dashboard create wizard calls this same endpoint as you move the interval slider.
Optional spend caps
Set spendCapCredits on create (or PATCH later) to cap what one monitor can spend in a calendar month. Once it hits the cap, further checks are skipped for the rest of the month — same skip-and-record behavior as running out of balance, scoped to that monitor.
Running low on credits
If the account doesn't have enough credits when a check comes due, the check is skipped, not failed. It's recorded in check history with a reason, and no charge happens. The monitor keeps trying on schedule. After 7 consecutive days of skipped checks, status flips to exhausted. Top up and it resumes on the next scheduled tick — no manual re-enable.
Plan limits
The only plan-gated limit is how many active monitors you can run. Poll frequency is not tiered — every eligible account can schedule down to the source's floor (currently 1 minute). Faster polling means more checks at the normal per-check price.
| Plan | Max active monitors |
|---|---|
| PAYG (no subscription) | 5 |
| Starter | 25 |
| Growth | 100 |
| Scale | 250 |
Limits are enforced at create, update, and resume. See Pricing for current plan details.