NAUT's crypto data API is live at https://api.naut.so/v1 for every account: mint a key from the account menu, confirm it with a free GET /v1/me, then pull people with GET /v1/people and funds with GET /v1/investors at 5 credits a call. Unlocking a person's private channels costs 10 credits the first time and 5 on every read after that, so a deal maker who wants a shortlist and 1 warm contact spends 20 credits end to end.
Every price, header, cap and endpoint below was read on NAUT's own API documentation on 27 October 2026, and every row count comes from the NAUT database on the same day. The API serves the same records the app serves, so what you see on naut.so/people and naut.so/investors is what a pull returns.
How much does the crypto data API cost per call?
The API bills in credits, the same credits the app's unlock button spends. NAUT's API pricing documentation puts it in 3 words: "One currency everywhere."
| Call | Credits | What it gives you |
|---|---|---|
GET /v1/me |
0 | The account behind the key, its plan, its live credit balance, and every endpoint with its own credit price |
GET /v1/people |
5 | Search and filter people, with the same filters as the app |
GET /v1/investors |
5 | Search and filter funds, 1 page of records at a time |
GET /v1/projects |
5 | Search and filter projects |
GET /v1/search |
5 | A single query across projects and people |
GET /v1/people/{id} |
10, then 5 | Add ?include=private for the first read of a person's email, phone, telegram or LinkedIn. A permanent unlock: later reads of that contact cost 5 and keep the channels |
So the credit question has a short answer. A read costs 5. Reaching a person costs 10. Checking your key costs nothing.
Credits arrive with a plan. The Essential plan is $49 a month for 3,000 credits, which NAUT's API pricing documentation counts as 600 data calls or 300 private reveals, and a mix of the 2 works out the same way. Unused credits "roll over up to twice your monthly grant", and Enterprise accounts "bypass credit charges entirely" while staying inside the rate limits below. Current prices sit on naut.so/pricing.
How do you mint a crypto data API key?
There is no separate developer signup. Any account that can sign in to NAUT can generate a key from the account menu under API, give it a label, and copy it.
A few things worth knowing before you put a key in a script:
- A key starts with
ck_live_, and the app afterwards lists it by that prefix only, so you can tell keys apart without exposing the full value. - The full key appears 1 time, at the moment you create it. NAUT stores a one way hash of it, so a lost key is revoked and replaced, never recovered.
- An account holds up to 10 active keys. Use 1 key per system so you can revoke a single integration without disturbing the rest.
- Every key is minted with both scopes the API uses:
read:metadatafor data and search calls, andread:contactsfor revealing a person's private channels. Scopes are not configurable today. - The key travels as a bearer token:
Authorization: Bearer ck_live_.... A missing, malformed or revoked key returns401 Unauthorized.
- Mint the keyOpen the account menu, choose API, generate a key labelled for 1 system. It starts with ck_live_ and shows in full once.
- Confirm it freeGET /v1/me returns the account, plan, live credit balance and every endpoint with its credit price, at 0 credits.
- Pull the shortlistGET /v1/people or GET /v1/investors costs 5 credits and returns 30 records a page, up to 100 with a limit.
- Unlock 1 contactGET /v1/people/{id}?include=private costs 10 credits once, then 5 on later reads, and keeps the channels.
The 3 calls that find a person or a fund
Call 1 confirms the key. GET /v1/me is free and returns apiVersion, the base URL, the docs URL, the account, the plan tier, the live credit balance, the key's label and scopes, and an endpoints array listing every path with its credit price. NAUT generates that array from the same price table that bills you, so the prices in the response are the prices you pay. It is also the reason to read the host and the docs link from the response rather than hard coding them.
Call 2 builds the shortlist. GET /v1/people searches and filters people, and supports q, roles, channels, contact type and sort. Private channels stay out of a list response, so a list call is 5 credits whatever the records contain.
Call 3 does the same for the money. GET /v1/investors searches and filters funds, and GET /v1/investors/{slug} returns 1 fund with its team and its portfolio, also 5 credits. The slug is the one in the fund's NAUT URL, so /v1/investors/galaxy-ventures returns what 
Galaxy Digital (Ventures) shows on the site, and /v1/investors/a16z-crypto and /v1/investors/sequoia-capital do the same for 
a16z crypto and 
Sequoia Capital. A founder raising works call 3 first, then call 2 on the partner names it surfaces. A BD lead selling into projects runs GET /v1/projects instead and checks the teams at naut.so/projects; a service provider hunting mandates starts at naut.so/services.
Pagination is the same everywhere. List endpoints return an envelope with data, total, page, limit and totalPages. A page is 30 records by default, and a limit outside 1 to 100 is clamped, with the response reporting the size that was used. A 10,000 record sweep is therefore 100 calls at a limit of 100, or 500 credits.
Every response carries a Compass-API-Version header naming the build that served it. It read 1.6.0 on 27 October 2026, and it is additive semver, so a minor version tells you which fields are populated rather than absent.
What a crypto data API pull reaches on NAUT
The calls are only worth their credits if the records behind them are real. These are the live rows in the NAUT database on 27 October 2026, the set those 3 calls search:
| What a pull reaches | Live rows |
|---|---|
| People | 14,350 |
| People with their own NAUT profile page | 11,650 |
| People with a LinkedIn on file | 9,074 |
| People with an X account on file | 8,794 |
| People with a Telegram on file | 6,884 |
| Projects | 6,923 |
| Funds | 3,360 |
| Funds with at least 1 live team contact | 339 |
Read the Telegram number next to the LinkedIn number, because that is the practical difference in crypto deal making. 6,884 of the 14,350 people on file carry a Telegram handle, which is where a crypto BD conversation actually starts. The 339 funds that already hold a live team contact are the shortlist a founder should work first: a fund page with a named person on it is a fund you can reach this week.
A crypto contact data pull is priced per call, not per record, so the 30 records in a default page cost the same 5 credits as the 1 record you were after. Filter hard, page deliberately, and cache what you have already pulled.
Rate limits, reveal caps and an empty balance
Rate limits apply per account. The ceiling is 120 requests a minute on every plan except Team, which gets 300 a minute, and Enterprise, which is capped at 5 requests a second. Minting a second key gives you a second label and a second thing to revoke, with the same allowance. Go over and the API returns 429 Too Many Requests. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, so you can pace a job without guessing.
Reveals have their own ceiling on top of the credit price: 600 an hour on a paid plan and 60 an hour on free. It is the same ceiling the app's unlock button uses, and re-reading a contact you have already unlocked does not count against it.
Failed authentication is bounded separately, per IP: more than 20 requests a minute carrying a key NAUT cannot resolve returns 429 from that address. It counts failures only, so a correct integration never meets it. Confirm a key once with GET /v1/me before you put it in a loop.
An empty balance behaves 2 ways. A call with too few credits returns 402 Payment Required and charges nothing. A free account holding fewer credits than the call costs instead receives clearly marked sample data, "sample": true with a Compass-Sample: true response header, at 0 credits: synthetic records shaped exactly like live ones, so an integration can be built and tested before a single credit is spent. The sampleMode field in the GET /v1/me response tells you which side of that line you are on.
The documentation lives at naut.so/docs/api, the key page sits in the account menu, and naut.so/developer is the public entry point.
Crypto data API FAQ
How much does a crypto data API cost?
On NAUT, as of 27 October 2026, a data or search call costs 5 credits, revealing a person's private channels costs 10 credits the first time and 5 after that, and GET /v1/me is free. Credits come from a plan: Essential is $49 a month for 3,000 credits, which NAUT counts as 600 data calls or 300 private reveals.
How do you get a NAUT API key?
Sign in to NAUT, open the account menu, choose API, and generate a labelled key. The key starts with ck_live_, displays in full exactly once, and an account can hold up to 10 active keys at a time, each revocable on its own.
What can you pull from the NAUT API?
People, projects, funds and service providers, plus a cross search over projects and people, all under /v1. On 27 October 2026 that covered 14,350 live people, 6,923 projects and 3,360 funds, of which 339 funds already had at least 1 live team contact attached.
What are the NAUT API rate limits?
120 requests a minute per account on every plan except Team at 300 a minute and Enterprise at 5 requests a second, with 429 Too Many Requests over the line. Private channel reveals carry a separate ceiling of 600 an hour on a paid plan and 60 an hour on free, measured as of 27 October 2026.
Are API credits separate from app credits?
No. NAUT's pricing documentation states "One currency everywhere", and there is no separate API subscription: a plan grants credits, the app's unlock button and the API spend the same pool, and unused credits roll over up to twice the monthly grant.
The data note
Prices, scopes, headers, caps and endpoint paths were read on NAUT's own API documentation at naut.so/docs/api on 27 October 2026, and the live Compass-API-Version header read 1.6.0 the same day. Row counts are a direct read of the NAUT production database on 27 October 2026, counting live records only. A connections graph endpoint, GET /v1/network, is listed as planned and was not tested. Prices and limits can change, and GET /v1/me is the version of record: it returns the endpoint list generated from the table that bills you, for free.