Clay: Argorant as an HTTP API enrichment column

Clay's native HTTP API column speaks the Argorant REST API directly, so Argorant becomes another enrichment step in a table you already have.

1. Mint an API key under Profile, API keys.
2. In your table, add an enrichment column, then HTTP API.
3. Set the header Authorization to Bearer <your key>.
4. Point it at the endpoint you need and map your table columns into the request fields.
5. Run the column. Each row returns clean JSON that downstream Clay columns can read.

Useful column shapes

• Verify an address you already have with POST /api/mcp/email/verify, mapping the row's email into the body. Branch the rest of the table on the deliverable flag.
• Qualify a company with the company people endpoint, mapping the row's domain into the path. You get people count and business-email coverage per account.
• Reveal a contact with GET /api/mcp/people/reveal and a limit of one, when the row already identifies the person you want.

Cost discipline in a table

Counts, previews and company lookups are free, so put those columns first and filter the table down before any column that spends. A reveal column on a 5,000-row table is a 5,000-credit decision, and Clay will happily run it. Filter, then enrich.