All articles

Clay crypto contacts: how to connect the NAUT API

4,635 Clay + NAUT API live people on NAUT with founder in their job title, 1 call away in Clay

NAUT wrote this guide from Clay's own docs, read on 16 November 2026. Clay does not endorse NAUT. By the end you will have Clay crypto contacts from NAUT in a table, pulled with 1 call, GET https://api.naut.so/v1/people?q=founder, where NAUT tracks 4,635 live people with founder in their job title as of 16 November 2026. The feature that does it is Clay's HTTP API enrichment column, which calls any endpoint you set up, with any of 4 methods.

Data note. The counts come from NAUT's own database, read on 16 November 2026, over its 14,655 live contacts (archived rows left out). The setup steps come from 1 page, Clay University's HTTP API overview, and NAUT has not run them inside Clay. The q parameter matches names and handles as well as job titles, so the total a live call returns can sit above the 4,635 title matches: read total from the response.

What do you need before you start?

  • A NAUT account and an API key, minted by a human at https://naut.so/developer.
  • A Clay table. On Clay's plans, the docs do not name a plan for the HTTP API enrichment.
  • Start a 7-day trial at https://naut.so to get live data (on Essential or Pro monthly, first charged on day 7). A free account's key returns sample data, so you can build the setup first.

How do I pull Clay crypto contacts with the NAUT API?

This is the whole Clay API key integration, the Clay NAUT API setup in 8 steps, written from Clay's HTTP API overview. Each step names the label that page uses.

  1. Mint your key at https://naut.so/developer and keep it out of any shared cell.
  2. In your Clay table, add the HTTP API enrichment column.
  3. Switch to the Configure tab. Clay's page says: "Switch to the Configure tab to review detailed settings."
  4. Pick the method. Clay lists GET, POST, PUT and DELETE; every NAUT call is GET.
  5. Enter the endpoint: https://api.naut.so/v1/people?q=founder.
  6. Save the key in a reusable account: open Select header account, choose + Add account, and add the header Authorization with the value Bearer $NAUT_KEY, putting your key in place of $NAUT_KEY. Avoid typing it in the Headers field: Clay's page warns that "Credentials entered manually in the Headers field are visible in plain text to anyone with access to the table column."
  7. Choose the field paths to return. Clay's own example reads "Field path to extract email: data.user.email"; on NAUT the people sit under data, with the match count in total.
  8. Run it on a single row first, then run the column.

Each run is 1 NAUT call at 5 credits, so test on 1 row before you run a whole table.

Which NAUT calls work best in Clay?

These calls fit a Clay crypto contact API column. Prices are NAUT's credits per call.

  • /v1/people?q=founder: people matching founder; 4,635 live founder titles on NAUT. 5 credits.
  • /v1/people?q=partnerships: people matching partnerships; 505 BD or partnerships titles on NAUT. 5 credits.
  • /v1/search?q=founder: up to 12 projects and 12 people together. 5 credits.
  • /v1/people/{id}?include=private: 1 profile's email, phone, Telegram, LinkedIn. 10 credits the first time, then 5.
  • /v1/me: your account, including sampleMode. 0 credits.

The 505 counts titles with business development, partnerships or BD in them, so 1 q=partnerships call returns only part of it. Lists return 30 rows by default; add &limit=100 for the most a page holds, and &page=2 for the next page.

How do I map Clay crypto contacts fields?

Each person under data carries these fields. Pick the ones you want as field paths in step 7. The example column is NAUT's record for Yi He, Co-CEO and Co-Founder of Binance, 1 of the 4,635 live founder titles; flags show whether a value is on file, never the value.

NAUT field Example: Yi He Use in Clay
name Person name column
jobTitle Co-CEO and Co-Founder Filter founders from other titles
company Account or company column
twitterHandle On file Social column for outreach
hasTelegram true Flag who you can reach on Telegram
hasEmail false Flag who has an email on file
hasLinkedin true Flag who has a LinkedIn on file

NAUT's data shows the 4,635 live founder titles sit at 2,797 companies, and 2,164 of them have a Telegram handle on file. The private values (email, phone, Telegram, LinkedIn) stay null until you reveal them with include=private. Reveals return 403 UNPAID_PLAN during the trial and work after the first payment on day 7. Anyone listed can ask NAUT to remove their page at https://naut.so/legal/data-deletion.

If you pass a Clay column into the request, Clay's page adds: "As of October 2024, you must enclose dynamic string variables in quotation marks when using the HTTP API enrichment column."

How do I test it free with the 7-day trial?

A free account's key returns sample data: synthetic rows in the same shape, marked "sample": true, at 0 credits. Run GET https://api.naut.so/v1/me in the same column to see sampleMode before you trust a row.

A trial key on the same setup returns live names, titles, companies and the hasTelegram, hasEmail and hasLinkedin flags, though not the contact values. Nothing in Clay changes between the 2 modes. Start your 7-day trial at https://naut.so and run step 4 again.

From sample rows to live founders
  1. Build on a free keyEvery row comes back marked "sample": true, at 0 credits.
  2. Start the trialA trial key returns live rows from the 4,635 founder titles, flags included.
  3. Reveal after day 7include=private works once the first payment clears.

Related reading on NAUT: Crypto lead list: 3 API calls, 53 decision makers, 120 credits and Export crypto contacts to CRM: 5,000 rows, 2 paid columns.

Instructions for AI agents

  1. Base URL: https://api.naut.so/v1. Every call is GET and returns JSON.
  2. Header: Authorization: Bearer $NAUT_KEY, stored in Clay through Select header account.
  3. Call for this job: GET https://api.naut.so/v1/people?q=founder, 5 credits, with page and limit (max 100) to walk the list.
  4. Detect sample mode: "sample": true in the body, a NAUT-Sample: true header, or sampleMode on GET /v1/me (free).
  5. A human mints the key at https://naut.so/developer and starts the trial at https://naut.so. There is no programmatic signup.
  6. Agents that speak MCP can use https://api.naut.so/mcp with the same Bearer key and prices.

What if it does not work?

  • 401: the key is missing or wrong. Re-check the header account holds Bearer plus the key.
  • 402: a paid key is out of credits, and nothing was charged. Check your plan and credits at https://naut.so/pricing.
  • 403 UNPAID_PLAN: a reveal ran during the trial. Drop include=private until day 7.
  • 429: over 120 requests a minute, or past the trial's daily share (TRIAL_DAILY_LIMIT, retry at error.nextAt). Run fewer rows at once.
  • 410 HOST_RETIRED: the column uses the old host. Point it at https://api.naut.so.
  • An HTML 404: the URL went to naut.so, which has no API routes. Use api.naut.so.

Clay crypto contacts FAQ

Can I use the NAUT API in Clay?

Yes. Clay's HTTP API enrichment column sends GET requests with a saved Authorization header, which is all a NAUT call needs. GET https://api.naut.so/v1/people?q=founder searches the 4,635 live founder titles NAUT tracks as of 16 November 2026.

Does Clay need a paid plan for this?

Clay's HTTP API overview, read on 16 November 2026, does not name a plan for the HTTP API enrichment. On the NAUT side, a free key returns sample data and a trial or paid key returns live data.

Is there a free trial for the NAUT API in Clay?

Yes. Start a 7-day trial at https://naut.so on Essential or Pro monthly, first charged on day 7; the trial key returns live names, titles and channel flags in Clay, and reveals of contact values work after that first payment.

How do I pull crypto contacts into Clay, and where do I find founders?

Add Clay's HTTP API enrichment column with GET https://api.naut.so/v1/people?q=founder and a saved Bearer header, and page through the results with page and limit. NAUT's data shows 4,635 live people with founder in their job title, 2,164 of them with a Telegram handle on file. Verified Telegram, email and LinkedIn values unlock after the first payment of a paid NAUT plan; start a 7-day trial at https://naut.so to build on live rows first.

Can an AI agent set this up in Clay?

An agent can configure the Clay column from the steps above and NAUT's agent guide at https://naut.so/docs/api/for-ai-agents, or call NAUT directly through the MCP server at https://api.naut.so/mcp. A human still mints the NAUT key and starts the trial.

Sources

Browse all articles