Crypto data for AI agents: 1 API, 2 calls, 15 credits

Crypto data for AI agents is a single read-only API: NAUT tracks 6,918 live projects, 3,337 investors, 158 service providers and 14,356 people as of 30 October 2026, and serves all of it to an agent over https://api.naut.so/v1 with a bearer key. An agent that starts from a company page and ends with a named decision maker and their private channels spends 2 calls and 15 credits, and it can rehearse the whole sequence on sample data for 0 credits before a card is ever charged.

Data note

Every count here comes from NAUT's own production database, read on 30 October 2026, and every price, parameter and limit comes from NAUT's API docs read on 31 October 2026: the API docs, the agent guide and pricing. The worked example uses 1 real company, Arcium (Elusiv), and the 3 contacts NAUT lists for it. NAUT stores 2 of those 3 titles as co-founder and 1 as ceo, with 1 of the co-founder strings carrying a stray character, so the titles below are given in clean form. Counts of channels are what NAUT holds on 30 October 2026, never a claim about what a person has elsewhere. Anyone named on NAUT can ask for their record to be removed at naut.so/legal/data-deletion.

What crypto data for AI agents does NAUT hold?

4 record sets, ranked by how many rows each held on 30 October 2026. Each one answers to its own endpoint, and every call in the table costs 5 credits.

Crypto people data is the half most agents are sent to fetch. Of the 14,356 people, 8,811 carry an X handle and 6,990 carry a Telegram handle, so an agent asked for a route to a human has a public channel for most of the set and a messaging channel for close to half of it. A person record also carries jobTitle, twitterHandle, company and the flags hasEmail, hasPhone, hasTelegram and hasLinkedin, which is what lets an agent decide whether a reveal is worth paying for before it pays.

How does an agent go from a company to its decision maker?

In 2 calls. Ask for the company by its slug, read its team, pick the title that can say yes, then reveal that 1 person. Run against Arcium (Elusiv), a confidential computing network, the sequence looks like this.

Step 2 costs 10 credits the first time an agent unlocks that person and 5 every time after, because the unlock is permanent. GET /v1/me is free, so an agent can call it without spending anything.

Which of the 3 contacts should the agent pick?

All 3 are founders or the chief executive, listed CEO first, then the 2 co-founders. NAUT's own channel flags are what separate them.

Contact	Title on NAUT	X	Telegram	LinkedIn
Yannik Schrade	CEO	yes	yes	yes
Nico Schapeler	Co-founder	yes	yes	yes
Julian Descher	Co-founder	yes	yes	no

An agent told to reach the person who signs picks Yannik Schrade, the CEO, and spends its 10 credits once. An agent told to open a technical conversation has 2 co-founders to choose from and the same cost. None of the 3 carries an email on NAUT as of 30 October 2026, so the first message goes on Telegram or X.

How do you test crypto data for AI agents for 0 credits?

Run in sample mode. A key without enough credits gets back clearly marked sample data: synthetic rows in the same shape as the real thing, for 0 credits. An agent builder can wire the parser, the title logic and the message template against that, confirm the sequence works end to end, then top up and run the identical code against live records. A paid key that runs short mid-task gets HTTP 402 and is charged nothing, so a half-finished job never silently bills. A crypto API for AI agents is only worth wiring up if it can be rehearsed before it is paid for, and this is how NAUT does that.

What should an agent never do with this data?

3 limits, all worth hard-coding into the agent before it reaches production.

• Never reveal in bulk. A reveal is a 10 credit unlock on 1 named person for 1 named reason. Walking a 14,356 row set and unlocking everything is both the most expensive thing an agent can do and the least useful: the value is the 1 person who can say yes.
• Never ignore the rate limit. 120 requests a minute per account, 300 on the Team plan. An agent that fans out in parallel across a list can pass it, so queue the calls and stay under it.
• Never pay to learn a flag already in the 5 credit response. hasEmail, hasTelegram, hasLinkedin and hasPhone are on every person record. Check the flag, then reveal only when the channel the agent needs is actually there.

What this gives a BD team or a founder raising

• A BD lead gets a shortlist that resolves to people. Used as a web3 contacts API, NAUT holds 14,356 people as of 30 October 2026, and a project page such as Arcium (Elusiv) names its CEO and 2 co-founders.
• A founder raising points the agent at /v1/investors instead, 3,337 funds, and gets each fund's team and its portfolio rows with round type, amount, announce date and lead flag from /v1/investors/{slug}.
• Either way the human-readable version of the same row is on naut.so, so a researcher can check what the agent returned: the agent read Arcium (Elusiv) and a person can open the same page.
• Budget is simple to plan: at 5 credits a call, the $49 Essential plan's 3,000 credits is 600 data calls a month, and a 2 call task like the one above, with a first-time reveal each run, fits at most 200 times.

Can you pull this data through the NAUT API?

Yes, and this article is 2 calls. GET https://api.naut.so/v1/projects/arcium-elusiv returns Arcium (Elusiv) with its team for 5 credits, then GET https://api.naut.so/v1/people/{id}?include=private reveals 1 of them for 10 credits the first time. Both are GET with Authorization: Bearer $NAUT_KEY. The counts in the first table were read from NAUT's database on 30 October 2026; each list call such as GET https://api.naut.so/v1/people?limit=1 returns a total you can read against them. The plans are on pricing with the full reference at naut.so/docs/api. Verified Telegram, email and LinkedIn for the people on NAUT unlock on any paid plan: start a 7-day trial.

Crypto data for AI agents FAQ

How do I give my AI agent crypto people and company data?

Mint a key at naut.so/developer, point the agent at https://api.naut.so/v1 with a bearer header, and read the agent guide. That 1 API covers 6,918 projects, 3,337 investors, 158 service providers and 14,356 people as of 30 October 2026, at 5 credits a call.

Where can I find crypto founders and their contact channels?

On NAUT's people and project pages, and through the same 2 calls an agent uses. NAUT holds 14,356 people as of 30 October 2026, 8,811 with an X handle and 6,990 with a Telegram handle, and the private channels on 1 profile unlock for 10 credits through GET https://api.naut.so/v1/people/{id}?include=private.

What does a crypto data API call cost?

5 credits for any data or search call, 10 credits the first time an agent reveals 1 person's private channels and 5 after that, and 0 for GET /v1/me. Essential is $49 a month for 3,000 credits, which is 600 data calls; Pro is $99 for 6,000 and Team $249 for 15,000.

Can an agent test the API without paying?

Yes. A key without enough credits returns clearly marked sample data in the same shape for 0 credits, and a 7-day free trial grants credits. A paid key that runs short returns HTTP 402 and is charged nothing.

How many contacts does NAUT list for 1 company?

It varies by company. Arcium (Elusiv) lists 3 as of 30 October 2026, all of them founders or the CEO. Across the whole database NAUT holds 14,356 people and 6,918 live projects.

Sources

• NAUT's own production database, read on 30 October 2026: live counts of projects, investors, service providers and people, the X and Telegram coverage of those people, and the team rows and channel flags for Arcium (Elusiv).
• NAUT's API documentation, read on 31 October 2026: the API reference, the agent guide and the plans and credits. Prices, query parameters, rate limits and the sample data behaviour above are taken from those pages only.