
NAUT wrote this guide from OpenAI's own docs for Custom GPT Actions, read on 16 November 2026. OpenAI does not endorse NAUT. By the end you will have Custom GPT crypto contacts from NAUT in a chat, 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 the API Key option under an Action's authentication in the GPT editor.
Data note. The counts come from NAUT's own database, read on 16 November 2026, over its 14,680 live contacts. The setup comes from 1 page, OpenAI's Actions authentication doc, and NAUT has not run it inside a Custom GPT. That page confirms the auth options and how the key is stored; it does not walk through the other editor screens, so this guide leaves their labels out. The q parameter matches names and handles as well as job titles, so the total a live call returns can differ from 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 Custom GPT you can edit in the GPT editor. On ChatGPT plans, the docs do not name a plan: the authentication page NAUT read states none.
- 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 Custom GPT crypto contacts with the NAUT API?
This is the whole Custom GPT API key integration, the Custom GPT NAUT API setup in 6 steps. Only the labels OpenAI's authentication page confirms are named.
- Mint your key at https://naut.so/developer and keep it out of the GPT's instructions.
- Open your GPT in the GPT editor and add an Action for NAUT.
- Describe 1 GET operation on the server
https://api.naut.so/v1with the path/peopleand aqquery parameter, so the GPT can callhttps://api.naut.so/v1/people?q=founder. The authentication page does not cover this schema step; follow OpenAI's Actions docs for its format. - Set the Action's authentication. OpenAI's page says to "use the GPT editor and select "None", "API Key", or "OAuth"." Pick API Key.
- Enter your NAUT key there, set up so every call sends
Authorization: Bearer $NAUT_KEYwith your key in place of$NAUT_KEY. The page NAUT read does not name the auth type controls, so check that the setting you pick sends the key as a Bearer token. On storage, OpenAI's page says: "We encrypt the secret key when we store it in our database to keep your API key secure." - Test the GPT with a prompt asking for founders, then check the reply. Each call is 5 NAUT credits.
Which NAUT calls work best in Custom GPT?
These calls fit a Custom GPT crypto contact API Action, priced in NAUT credits.
Every path below starts with /v1.
| Call | What it returns, and its credits |
|---|---|
/people?q=founder |
People matching founder; 4,641 live founder titles on NAUT. 5 credits |
/people?q=partnerships |
People matching partnerships; part of 308 BD or partnerships titles. 5 credits |
/search?q=founder |
Up to 12 projects and 12 people together. 5 credits |
/people/{id} |
With include=private: 1 profile's email, phone, Telegram, LinkedIn. 10 credits first time, then 5 |
/me |
Your account, including sampleMode. 0 credits |
The 308 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 (max 100) and page to the operation so the GPT can ask for more.
How do I map Custom GPT crypto contacts fields?
Each person sits under data in the JSON the Action returns, and the GPT reads those fields to answer in chat. Name them in the GPT's instructions so its replies keep the same order. The example column is NAUT's record for Yi He, Co-CEO and Co-Founder of Binance, 1 of the 4,641 live founder titles.
| Field | Yi He | How the GPT uses it |
|---|---|---|
name |
Lead each answer line | |
jobTitle |
Co-CEO and Co-Founder | Keep founders only |
company |
Group people by project | |
twitterHandle |
On file | Link the X profile |
hasTelegram |
true | Say who has Telegram |
hasEmail |
false | Say who has email |
hasLinkedin |
true | Say who has LinkedIn |
NAUT's data shows 2,164 of the 4,641 live founder titles have a Telegram handle on file. The flags show whether a value is on file, never the value. 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.
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 GET https://api.naut.so/v1/me as a second operation and ask the GPT for sampleMode before you trust a row.
A trial key on the same Action returns live names, titles, companies and the hasTelegram, hasEmail and hasLinkedin flags, though not the contact values. Only the key changes. Start your 7-day trial at https://naut.so and run step 4 again.
- Build on a free keyEvery row comes back marked "sample": true, at 0 credits.
- Start the trialA trial key returns live rows from the 4,641 founder titles, flags included.
- 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 lead list: 3 API calls, 53 decision makers, 120 credits.
Instructions for AI agents
- Base URL:
https://api.naut.so/v1. Every call is GET and returns JSON. - Header:
Authorization: Bearer $NAUT_KEY, stored through the Action's API Key authentication, never in the GPT's instructions. - Call for this job:
GET https://api.naut.so/v1/people?q=founder, 5 credits, withpageandlimit(max 100) to walk the list. - Detect sample mode:
"sample": truein the body, aNAUT-Sample: trueheader, orsampleModeonGET /v1/me(free). - A human mints the key at https://naut.so/developer and starts the trial at https://naut.so. There is no programmatic signup.
- 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-enter it under API Key and check it goes out as
Bearerplus 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. Dropinclude=privateuntil day 7. - 429: over 120 requests a minute, or past the trial's daily share (
TRIAL_DAILY_LIMIT, retry aterror.nextAt). Ask the GPT for fewer pages at once. - 410
HOST_RETIRED: the Action uses the old host. Point the server athttps://api.naut.so. - An HTML 404: the server URL is naut.so, which has no API routes. Use
api.naut.so.
Custom GPT crypto contacts FAQ
Can I use the NAUT API in a Custom GPT?
Yes. OpenAI's Actions authentication page lists API Key as 1 of 3 options in the GPT editor, and a NAUT call needs only a Bearer key and a GET. GET https://api.naut.so/v1/people?q=founder searches the 4,641 live founder titles NAUT tracks as of 16 November 2026.
Does a Custom GPT need a paid ChatGPT plan for this?
OpenAI's Actions authentication page, read on 16 November 2026, does not name a ChatGPT plan for Actions. 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 a Custom GPT?
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 your Custom GPT, and reveals of contact values work after that first payment.
How do I pull crypto contacts into Custom GPT, and where do I find founders?
Add a NAUT Action with API Key authentication and GET https://api.naut.so/v1/people?q=founder, then page through the results with page and limit. NAUT's data shows 4,641 live people with founder in their job title, 2,164 of them with a Telegram handle on file. Their 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 a Custom GPT?
An agent can draft the Action from these steps and NAUT's agent guide at https://naut.so/docs/api/for-ai-agents, or use the MCP server at https://api.naut.so/mcp. A human still mints the NAUT key and starts the trial.
Sources
- OpenAI, Actions authentication, read 16 November 2026: https://developers.openai.com/api/docs/actions/authentication
- NAUT API docs: https://naut.so/docs/api
- NAUT plans and trial terms: https://naut.so/pricing
- NAUT database, read-only, 16 November 2026: 14,680 live contacts, 4,641 with founder in their job title, 2,164 of those with Telegram on file, 308 with business development, partnerships or BD titles.