Counts do not deduct contact credits but require permission and remain rate-limited. This endpoint counts matching contact records, not unique companies or already-verified deliverable addresses.
curl -G -H "Authorization: Bearer ag_live_..." \
--data-urlencode "keywords=logistics" \
--data-urlencode "country=Germany" \
--data-urlencode "seniority=vp" \
https://app.argorant.com/api/mcp/people/countParameters
Filters are passed as query parameters. The set mirrors what the CLI exposes:
- Free text:
q - Role:
title,exclude_title,seniority,departments - Firmographics:
industry,keywords,company_name,company_domain - Geography:
country(regions such as Europe, EMEA, DACH, Nordics, APAC, LATAM and GCC expand into their member countries),state,city - Data presence:
has_email,has_phone,has_linkedin,verified_only
keywords is the widest and most reliable filter, with comma meaning OR. Prefer it over industry when a count comes back smaller than you expected.

The response carries the count. The equivalent CLI call is npx argorant count --keywords logistics --country Germany --json.
One caveat worth knowing: exclude_title is applied on export and list creation, but not yet on the count path. The CLI prints a note about this rather than silently dropping the filter.