linkspect API docs linkspect.com

Limits and usage

Each account has limits on how much it can measure. They apply to the account as a whole: all its keys share them. The one exception is the request rate, which each key has on its own. Test checks count against the daily and concurrent limits too, so a test loop can use up the checks of the day.

The limits

The values below are the defaults of a new account. Yours may be different: GET /v1/usage shows them.

Limit (limit)DefaultWhat it countsWhen reached
checks_per_day1000Checks created per UTC day, test and live, monitor checks included.429 quota-exceeded until midnight UTC.
cohorts_per_check50Cohorts in one check, after the targets are expanded.422 too-many-cohorts: split the check.
proxy_bytes_per_day200 000 000 (200 MB)Proxy traffic of live measurements per UTC day, home and mobile together. Test checks use none.Live cohorts come back not_measured with reason quota_exceeded, see below.
browser_checks_per_day100 (10 for a paid account)Live checks with browser per UTC day. Test keys never open browsers, so their checks do not count. For a paid account they are free, up to 10 a day.429 quota-exceeded until midnight UTC.
concurrent_checks10Checks of the account not finished yet, test and live.429 quota-exceeded; retry when one of them finishes (Retry-After: 10).
requests_per_minute100Requests of each API key. See Rate limits.429 rate-limited, usually for a second.
monitors20Monitors of the account, test and live together.422 too-many-monitors: delete one first.
live_checks_per_daynoneChecks made with live keys per UTC day. Once they are used up, a live check takes one of the account's check_credits.429 quota-exceeded until midnight UTC, when no credits are left.
proxy_bytes_per_monthnoneProxy traffic of live measurements per UTC calendar month.Live cohorts come back not_measured with reason quota_exceeded until the first of the next month.
countries_per_checknoneCountries in one check.422 too-many-countries: make one check per country.

Trial accounts

An account made by the trial sign-up on linkspect.com has its own limits: 15 live checks on its first day, then 3 a day: 3 live checks a day plus 12 check credits it gets with its live key, used once the day's 3 are (check_credits in GET /v1/usage; they do not reset, and unused daily checks do not pile up), one country per check, one check at a time, one browser check a day, no monitors, and at most 100 MB of proxy traffic a day and 250 MB a month. A live check that gives no answer we would charge for (our side failed, the result was unclear, or the site turned our test away) gives its check back. Test keys of a trial account have up to 100 checks a day.

Webhooks are limited too: at most 10 for the test keys of an account and 10 for its live keys. An eleventh gets 422 invalid-request.

Daily limits count per UTC day and start again at midnight UTC. A check is counted when it is created, with all its cohorts; a check you cancel still counts.

When the day's proxy traffic is used up

Before each live cohort is measured, it sets aside an estimate of its proxy traffic (250 KB) from what is left of the day; when it finishes, the estimate is replaced by the traffic it really used. A cohort that cannot set aside its estimate is not measured: it comes back not_measured with reason quota_exceeded, uses no traffic and is not charged.

New checks are still accepted while the traffic is used up, as long as the other limits allow them, but their live cohorts come back not_measured until midnight UTC. Check today.remaining.proxy_bytes before you start a large check.

See your usage: GET /v1/usage

curl "https://api.linkspect.com/v1/usage?from=2026-11-15&to=2026-11-16" \
  -H "Authorization: Bearer $LINKSPECT_KEY"

Without from and to, you get the last 30 days. Every key of the account sees the same numbers.

{
  "account": {"id": "acc_01M6Z8Q5V0K3T7N2B9C4D6E8F1", "name": "Acme Monitoring"},
  "from": "2026-11-15",
  "to": "2026-11-16",
  "days": [
    {"date": "2026-11-15", "checks": 12, "test_checks": 2, "cohorts": 58, "browser_checks": 1,
     "user_filter_queries": 10, "proxy_bytes": {"fixed": 4812330, "mobile": 1204118}},
    {"date": "2026-11-16", "checks": 5, "test_checks": 0, "cohorts": 20, "browser_checks": 0,
     "user_filter_queries": 5, "proxy_bytes": {"fixed": 2150007, "mobile": 640221}}
  ],
  "limits": {"checks_per_day": 1000, "cohorts_per_check": 50, "proxy_bytes_per_day": 200000000,
             "browser_checks_per_day": 100, "concurrent_checks": 10, "requests_per_minute": 100,
             "monitors": 20, "live_checks_per_day": null, "proxy_bytes_per_month": null,
             "countries_per_check": null},
  "check_credits": 0,
  "today": {
    "date": "2026-11-16",
    "remaining": {"checks": 995, "proxy_bytes": 197209772, "browser_checks": 100, "live_checks": null},
    "active_checks": 0,
    "monitors": 0,
    "resets_at": "2026-11-17T00:00:00Z"
  },
  "billing": {"enabled": false, "currency": "USD", "balance": "0.00", "reserved": "0.00",
              "available": "0.00", "discount": null, "free_browser_checks_per_day": null,
              "days": [{"date": "2026-11-15", "charged": "0.00", "charged_checks": 0},
                       {"date": "2026-11-16", "charged": "0.00", "charged_checks": 0}]}
}

Monitor checks count like any other check. When a scheduled monitor check is skipped over a daily limit, you get one monitor.quota_exceeded event per monitor and day (see Monitors and webhooks).