Usage

This month

Your plan, what it allows and what you have spent against it — the same numbers the API returns, broken down by key.

Checking usage from code

GET /usage returns all of it. Worth calling at the start of a long job: if the month's allowance cannot cover the work, you would rather know before you start than half way through.

curl https://api.webbites.io/v1/api/usage \
  -H "Authorization: Bearer $WEBBITES_KEY"

{
  "tier": "plus",
  "limits": { "perMinute": 300, "perMonth": 20000 },
  "usage": {
    "month": 412,
    "total": 9031,
    "byKey": { "wb_live_…": 412 }
  }
}

const usage = await fetch(`${BASE}/usage`, { headers }).then(r => r.json())

const left = usage.limits.perMonth - usage.usage.month
if (left < urls.length) {
  throw new Error(`Need ${urls.length} requests, ${left} left this month.`)
}

What counts

• Requests you make against the API are what the allowance covers — every call in this list of endpoints, however small.
• Deliveries we send you are ours to make, not requests you made, which is the main reason to prefer a webhook over polling.
• Using the app, the extension or the native apps is not API traffic and does not appear here.
• Limits are per account, shared across every key. byKey tells you which key spent what.

Running out of month rather than out of minute? The plans are on the pricing section, and Rate limits lists what each one allows.