All articles

Relevance AI crypto contacts: how to connect the NAUT API

4,641 Relevance AI + NAUT API live people on NAUT with founder in their job title, 1 call away in Relevance AI

NAUT wrote this guide from Relevance AI's own docs, read on 16 November 2026. Relevance AI does not endorse NAUT. By the end you will have Relevance AI crypto contacts from NAUT inside a tool, pulled with 1 call, GET https://api.naut.so/v1/people?q=founder, where NAUT tracks 4,641 live people with founder in their job title as of 16 November 2026. The feature that does it is Relevance AI's API Tool step, which sends a custom API call to an outside service.

Data note. The counts come from NAUT's own database, read on 16 November 2026: 14,680 live people in total. The setup steps come from Relevance AI's API Tool step page (listed under Sources), and NAUT has not run them inside Relevance AI. The q parameter matches names and handles as well as job titles, so the total a live call returns can sit above the 4,641 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 Relevance AI account where you can build a tool. On Relevance AI's plans, the docs do not name a plan: the API Tool step page states no plan or tier for the step.
  • 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 Relevance AI crypto contacts with the NAUT API?

This is the whole Relevance AI API key integration, the Relevance AI NAUT API setup in 7 steps, written from Relevance AI's API Tool step page.

  1. Mint your key at https://naut.so/developer and keep it out of shared notes and chats.
  2. Add the step. Relevance AI's page says to start by "Creating a new Tool, then searching for the 'API' Tool step".
  3. Pick the method. The page says: "Select the method you wish to use for your API call". Set it to GET, the only method NAUT's API uses. The page's own examples show POST and PUT.
  4. Set the address. The page says: "Enter the URL / pathway / endpoint you want to call". Enter https://api.naut.so/v1/people?q=founder.
  5. Add the key as a header. The page says: "Add headers, body and URL parameters as needed for your API call", and its example header is "Authorization": "Bearer YOUR_TOKEN". Add Authorization: Bearer $NAUT_KEY, putting your own key where $NAUT_KEY sits. Leave the body empty. The page does not name a separate place to store an outside service's key, so the key lives in this header.
  6. Set the response format to json, from the list the page introduces with "Allows you to select the format of the response. You can choose from:". Tick the error option, which the page describes as: "When checked, throws an error when the API response contains a 4xx/5xx response code."
  7. Run the step once and read the response: the people sit under data, with the match count in total.

Each run is 1 NAUT call at 5 credits, so test once before an agent calls the tool in a loop.

Which NAUT calls work best in Relevance AI?

These calls fit a Relevance AI crypto contact API step. Every path below sits under /v1, and credits are NAUT's price per call.

Call What it returns Credits
/people?q=founder 4,641 founder titles 5
/people?q=partnership Part of 308 BD titles 5
/search?q=founder Up to 12 projects, 12 people 5
/people/{id} 1 profile's channels, with include=private 10, then 5
/me Your account, sampleMode 0

The 308 counts live titles with business development or partnership in them, so 1 q=partnership 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 Relevance AI crypto contacts fields?

With the response format set to json, each person under data in the step's output carries the fields below. The API Tool step page does not cover passing the output to later steps, so the right column is a suggested use inside your tool or agent. For example, NAUT's record for Paul Farhi carries the jobTitle CEO & Founder and hasTelegram true, so a Telegram route would keep him. Anyone listed can ask NAUT to remove their page at https://naut.so/legal/data-deletion.

Field Holds Use in Relevance AI
name Full name Contact name
jobTitle Current title Keep founders only
company Company Account field
twitterHandle X handle Social field
hasTelegram true or false Route Telegram leads
hasEmail true or false Route email leads
hasLinkedin true or false Route LinkedIn leads

NAUT's data shows 2,164 of the 4,641 live founder titles have a Telegram handle on file. The flags say whether a value is on file, never the value. 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.

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. Add a second API Tool step to GET https://api.naut.so/v1/me, with the same header, 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. 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,641 founder titles, flags included.
  3. Reveal after day 7include=private works once the first payment clears.

Related reading on NAUT: Clay crypto contacts: how to connect the NAUT API and Crypto data for AI agents: 1 API, 2 calls, 15 credits.

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, set in the headers of the Relevance AI API Tool step.
  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. Check the header reads Bearer, a space, then 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). Slow the agent down.
  • 410 HOST_RETIRED: the step 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.

Relevance AI crypto contacts FAQ

Can I use the NAUT API in Relevance AI?

Yes. A Relevance AI API Tool step takes a method, a URL and headers, which is all a NAUT call needs. GET https://api.naut.so/v1/people?q=founder searches the 4,641 live founder titles NAUT tracks as of 16 November 2026.

Does Relevance AI need a paid plan for this?

Relevance AI's API Tool step page, read on 16 November 2026, does not name a plan for the step. 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 Relevance AI?

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 Relevance AI, and reveals of contact values work after that first payment.

How do I pull crypto contacts into Relevance AI with an API key?

Put a NAUT key in the Authorization header of a Relevance AI API Tool step and call GET https://api.naut.so/v1/people?q=founder, which covers 4,641 live people with founder in their job title; NAUT's data shows 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 Relevance AI?

An agent can follow 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