REST: GET /api/mcp/people/reveal - Argorant Help

Reveal returns full contact records: name, job title, company, work email, phone number and LinkedIn URL where available. It costs one credit per revealed contact.

curl -G -H "Authorization: Bearer ag_live_..." \
  --data-urlencode "title=Head of Procurement" \
  --data-urlencode "country=Germany" \
  --data-urlencode "limit=25" \
  https://argorant.com/api/mcp/people/reveal

Parameters

All the filters from count and preview.
limit: how many contacts to reveal. This is your budget for the call. Treat it as such.

Use reveal when you want records back in the response, immediately, for a handful of people. Use an export when you want a verified CSV of hundreds or thousands of rows.

Reveal response with the full contact fields (sample data)

Before you call it

Count the segment. Free.
Preview it. Free.
Only then reveal, with an explicit small limit.

The CLI adds a confirmation prompt for humans at a terminal, but that prompt disappears in scripts, pipes and agent loops. Over REST there is no prompt at all. The row limit is the only guardrail, which is why agents should be instructed to name the number out loud before calling.

If the balance is empty the call returns 402 with the link to fix it, and no credits are consumed.