Count matching raw blocks (mass-unlock cost estimate)
Changed onReturn how many raw blocks match the given filters, i.e. the maximum number of parts (1 point each) a mass unlock would consume. Uses the same payload as /search/raw so the count matches exactly what search and unlock traverse.
This is intended to be called on demand (e.g. when opening the mass-unlock dialog), NOT on every search: the count is heavier than a page fetch and is cached.
- exact=true: total is the exact count.
- exact=false: total is an upper bound (q_exact and/or dedup shrink the real set).
- capped=true: the count hit its upper limit, so total is a lower bound.
Rate limit: shares the raw search limit, including its concurrent-request slot: a count fans out over every shard of the raw index, so it is billed against the same budget as /search/raw rather than the wider generic search limit.
Request
- Base URLhttps://api.leakradar.io
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Query parameters
Mark the count as an upper bound because the deduplicated view folds identical content (block_fp64) app-side.
Request body
Example request
{
"q": "example.com"
}Response
Count computed successfully.
Changes
- info
added the new optional request property
- info
- info
added the new optional request property
- info
added the new optional request property
- info
added the new optional request property
- info
added the new optional request property
- info