API Access and Quota Visibility
Know what you spend
Integrate Watcher with your own systems where your plan allows secure API access, and always know how much PageSpeed Insights quota organisations and sites consume. Visibility helps you right-size test frequency, forecast cost, and explain spikes when aggressive schedules or large URL sets push monthly limits.
Why it matters
Predictable ops, finance-friendly explanations, safer automation.
Usage you can read
See consumption across orgs and sites instead of guessing from invoices alone.
Plan-aligned access
API features follow your subscription tier.
Tune schedules with data
Pair visibility with scheduled testing to avoid surprise throttling.
What counts against quota
Quota reflects scheduled runs, mobile and desktop strategies where both are enabled, and any on-demand tests you trigger. Successful runs count toward your monthly allowance; failed attempts do not.
Illustrative usage bar
API surface (by plan)
| Topic | Summary |
|---|---|
| Authentication | Tokens or keys scoped to your plan; see API documentation when available. |
| Triggers vs reads | Separate endpoints for reading history and, where allowed, enqueueing new test runs. |
When finance asks why usage spiked
Tie visibility to portfolio growth, new sites, cadence changes, or failed retries. Watcher should be the place of record for consumption, not an opaque counter.