Overview
Estimate a whole keyword list for a brand: each keyword’s weekly US AI prompt volume, its Demand Score and its Commercial Intent score, the same numbers the Keyword Volume page in Scrunch shows. A list runs in the background. You start it, then poll it until it’s done; each keyword’s numbers appear as soon as it finishes.How it works
- Start a list of up to 200 keywords. You get its
idback at once. - Get the list about every 30 seconds until its
statusisfinished,failedorcanceled. Each keyword’s numbers appear as soon as it’s done, and stay readable after the list ends. - Cancel it if you started the wrong list. Keywords not yet estimated give their lookups back.
https://api.scrunchai.com/v1.
A brand runs one list at a time. A list of new keywords takes a few minutes; keywords estimated recently come back almost at once.
Authentication
Send an API key as a Bearer token. Create one in Scrunch under API Keys. Every endpoint needs thequery scope.
Start a list
- Up to 200 keywords, each up to 200 characters.
- Repeats (ignoring case and spacing) are counted once, and blank entries are dropped.
202) is the list, with its id and how many keywords are in each status:
Get the list
status is queued (waiting to start), running, finished, failed (stopped early) or canceled. Each keyword’s status is one of:
Result fields
weekly_estimate, demand_score and demand_label are null together when a keyword couldn’t be measured.
Cancel a list
canceled and their weekly lookups are given back. Finished keywords keep their results. Canceling a list that has already ended changes nothing.
Weekly lookups
Keyword Volume has a weekly allowance of lookups per brand, shared with lookups made in Scrunch itself.- Each keyword that hasn’t been estimated recently uses one lookup. Keywords estimated recently run without using one.
- A list bigger than what’s left isn’t refused. The keywords past the limit are marked
skipped_weekly_limit, in list order, and the rest run. - Lookups come back for a keyword that fails, is canceled, or turns out to have been estimated recently after all.
Status codes
Tips
- Poll every 30 seconds or so. Results land keyword by keyword; there’s no need to poll faster.
- Lost the
id? While the list runs, starting another returns409with the running list’s id atdetail.job_id. - Want a spreadsheet? Each keyword’s numbers are in
items[].result; write them out as CSV on your side. - Use the MCP server instead if you’re working in an AI assistant:
start_keyword_list,get_keyword_listandcancel_keyword_listdo the same thing.