peekpandaPeekPanda docs
Usage and limits
What the four usage tiles on the account desk count, which limits are actually enforced, and what happens when you reach one.
Download Markdown ↓The usage strip sits under your profile on /account. Four tiles, one row.
| Tile | What it shows |
|---|---|
| Refreshes today | Requested refreshes recorded for your account in the last day, over your plan's allotment |
| Daily allotment | The number your plan carries: one for Peak, three for Panda |
| Active keys | How many of your API keys are live right now |
| Last key use | The date of the most recent call made with any active key |
Without a plan, the first two tiles read Not collected · Needs a Peak or Panda plan rather than showing zero. Last key use reads No key has been used yet until a key is actually used.
What the allotment covers, and what it does not
The plan allotment is the quota for requested catalogue refreshes, the on-demand enrichment lane. The published refresh and limits page is the source of truth here, and it is explicit: the plan values of one and three, and the shared 100-request reserve quoted on the pricing page, are requested-refresh quotas. They are not enforced on estimate refresh.
They do not govern ASO refreshes. Refreshing a tracked app or a keyword in the ASO workstation is metered separately, and the counters for it live on the refresh pill inside the workstation, not on this strip. See refreshing keywords.
So read the strip as two independent things: a plan allotment for requested catalogue refreshes, and a live count of your API credentials.
The limits that are enforced
These are checked on every request, whichever surface asks.
ASO refreshes
| Limit | Value | What happens when you hit it |
|---|---|---|
| Your refresh jobs | 40 per UTC day | The request is refused with a rate-limit error and a retry time |
| Shared store calls | 2,500 per UTC day | The refresh pill returns cooldown until the next UTC midnight; no job is created |
| Per-app cooldown | 60 minutes | Only searches never collected before are fetched |
| Snapshot freshness | 24 hours | Anything newer is served from storage and costs nothing |
| Pacing | One store call every 4 seconds | Requests queue behind it |
Workstation size
| Limit | Value | What happens when you hit it |
|---|---|---|
| Tracked apps | 25 per account | The add box disables and tells you to stop tracking one first |
| Watched keywords | 100 per app | The batch is rejected whole, not partly saved |
| App name search | 20 per minute per account | The typeahead returns a rate-limit error until the minute rolls over |
Account
Creating an API key needs an active entitlement. Without one the create form is replaced by a line asking you to choose a plan. There is no limit on the number of keys.
Reading a usage number honestly
Every tile carries its provenance chip. Refreshes today, Active keys and Last key use are observed counts. Daily allotment is marked derived, because it is read off your plan rather than measured.
A tile with nothing behind it shows an em dash and the reason, never a zero.