Usage

Usage shows how much search and crawl activity a project is using.

Usage shows current-period plan consumption and search health for a project.

Main counters

Counter	Meaning
Indexed pages	Pages currently available to search.
Successful searches	Search API calls that completed successfully.
Failed searches	Search API calls that errored.
Total crawls	Manual and scheduled crawl runs.
Crawl pages checked	Pages fetched or checked during crawls.

Source usage

Use source usage to see which source consumes crawl volume.

For a Next.js project, a source that includes the full /docs/app tree will usually check more pages than a source limited to the single /docs/app/getting-started/installation page.

Monthly allowance

Your plan’s monthly allowance counts successful searches across the billing period. If a project reaches it, reduce unnecessary requests or move to a larger plan. The Search API returns 402 when the allowance is exhausted or billing is inactive.

Per-minute key limits

Per-minute key limits protect against short traffic bursts and accidental cost spikes. They are separate from the monthly allowance:

• Browser/public keys have a per-IP limit and a total-key limit.
• Server keys have a total-key limit only, because many visitors can share one server IP.
• The API returns 429 when an applicable per-minute limit is reached.

The defaults depend on the plan, but you can edit them when creating a key. See Search API Start Search API Auth, request fields, response shape, pagination, errors, and examples. for the current defaults and key behavior.

Quick checks

• Search volume high, indexed pages stable: visitors are using search.
• Crawl pages checked high, indexed pages flat: crawl scope may be too wide.
• Failed searches rising: check API auth, project id, and backend logs.