Track Semrush API unit consumption across report types to avoid mid-month quota exhaustion
domain: developer.semrush.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Check your API unit balance via the balance endpoint before running scheduled jobs
Note that unit cost varies by report/method and by whether you request live vs historical data - historical lookups can cost several times more per row than live equivalents
Export the API request/queries log (CSV) to see per-call unit cost and identify unexpectedly expensive calls
Batch and paginate large reports deliberately, since each returned row adds to the per-call unit cost
Align monthly unit purchases/add-ons with your plan's included allowance before scaling automated pulls
Known gotchas
The same report can cost very different unit amounts depending on live vs historical mode - don't assume a flat per-row price
Exhausting your unit balance stops API responses until the next billing cycle or a manual top-up
The report-cost field in the query log is your primary way to audit spend since pricing isn't uniform across endpoints
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?