Company endpoints answer account-level questions rather than people-level ones. All of them are free.
Counts and search
GET /api/mcp/companies/count
GET /api/mcp/companies/searchThese take the same firmographic filters as people search: keywords, industry, country, state, city, and company size. Use them when the question is how many companies match, not how many people.
People at one company
GET /api/mcp/companies/{domain}/peoplePass a bare domain such as stripe.com. Optional query parameters narrow the result: title, seniority, departments, country and limit.
What comes back
- The company record, including its reported employee estimate where available.
- How many people at that company are in the dataset.
- How many of them have business-email coverage, which is the number that predicts how many you could actually reach.
- A masked role preview of up to your limit, so you can see which functions exist before spending anything.

The CLI wraps this as one command:
npx argorant company stripe.com -n 5
npx argorant company stripe.com --title CFO --jsonThis is the fastest way for an agent to qualify a target account list: feed it domains, get back coverage numbers, and drop the accounts you cannot reach before you build any campaign around them.