Rate limits and usage

Requests per minuteCopy Anchor Link

Limits count per workspace and per product: Track calls never use up Enhance's budget, and the other way round. REST and MCP calls count together.

An Enhance plan that includes Track gets at least that Track plan's limit on its Track calls. Need more? Contact us about a custom limit.

On Enhance, calls that start, stop, restart or delete campaigns are also limited to 10 a minute per key.

Lookup limits (Track)Copy Anchor Link

Some Track calls do more work, so they also have hourly limits per workspace:

Over the limitCopy Anchor Link

You get 429 and a Retry-After header with the seconds to wait (60 for the per-minute limits):

HTTP/1.1 429 Too Many Requests
Retry-After: 60
Content-Type: application/json

{"error":"rate_limited"}

The lookup limits answer 409 with {"code": "rate_limited"}. There are no other rate-limit headers: keep your own count, or simply wait when you see 429.

Good habits:

• Poll scans every 15 to 30 seconds, not in a tight loop.
• Read one campaign's scans (GET /v1/track/campaigns/{id}/scans) instead of every campaign each time.
• Back off when you see 429, and retry after Retry-After.

What calls costCopy Anchor Link

API and MCP calls themselves are not charged. What they do is:

• Track scans spend points. One point per grid point, or one per keyword on a website campaign. Some engines and every AI answer cost more. GET /v1/track/usage shows points used this month, bought points left and left, everything you can still scan. GET /v1/track/engines shows the cost of each engine on your plan.
• Enhance campaigns use your plan while they send visits, the same as when you start them in the panel.

Monthly points renew on the first day of each month (UTC). When the month's points run out, bought points are used. A run that needs more than you have left is refused with 409 quota before it starts.