The people data API for AI agents.
The core operation is a two-stage pipeline - resolve the identity first, then enrich it - with a published confidence score on the match and per-field sourcing and timestamps, which is a more honest data shape than a flat record. Note what kind of data this is: alongside B2B firmographics it returns household composition, household income band, property, wealth and affinities, which puts it in consumer-data territory as much as sales-tooling territory.
Engineering teams building agents or data pipelines that need to resolve messy identity fragments into complete person records - CRM enrichment, lead generation, and research or personalisation workflows that consume data programmatically rather than through an interface.
Two structural constraints. First, the API is asynchronous by design: most enrichment and search endpoints return 202 Accepted with a request_id and require you to poll a status endpoint or supply a callback_url, so anything expecting a synchronous blocking call needs rearchitecting - the advertised 184ms median enrich time is not the shape of a single round trip you can rely on inline. Second, rate limits are documented at 100 requests/minute and 1,000/hour, which caps bulk backfill work at roughly 24,000 records a day before you talk to sales. Separately, and more importantly for buyers in regulated or EU contexts: the returned record includes household composition, household income, wealth, property and affinity data on named individuals, which is consumer personal data with its own compliance burden - this is not a fit for a team that assumed it was buying B2B firmographics only.
No curated rival set covers this tool yet, so these are simply other tools in the same architectural layer and product form. Treat it as a starting point, not a shortlist.
An API key and secret sent as two HTTP headers, X-API-Key and X-API-Secret, generated from the dashboard. Nyne's docs explicitly warn never to ship the secret to the browser and to call the API from your backend.
Mostly not. The docs state that most enrichment and search endpoints are asynchronous: you submit and receive 202 Accepted with a request_id, then poll the matching status endpoint until status is 'completed', or supply a callback_url to receive the result by webhook instead.
100 requests per minute and 1,000 per hour, per the API documentation index.
No. The documentation states plainly that empty results never burn credits, and that completed results are charged according to the endpoint's credit table.
We could not retrieve any prices. Per-endpoint credit costs are documented within the API reference, but the cost of a credit is not something we obtained. Ask the vendor.
The vendor lists demographics, household composition, income and wealth, residence, property, affinities, career and company, filings, and live life-event signals - advertised as 2,400+ attributes, with each field scored, sourced and time-stamped, and a match confidence value on the resolution itself.
Both, and buyers should be clear-eyed about it. Alongside company firmographics, the advertised person record includes household size, household income band, residence, property and personal affinities on a named individual. That is consumer personal data, and it carries a different compliance and privacy posture than B2B contact enrichment.
As vendor marketing. We did not test any of it - and note the async submit/poll pattern means 184ms is not the end-to-end latency you will experience.
This page tells you whether Nyne.ai fits. Cheetah builds and runs the system it goes into — enrichment, sequencing, CRM and the joins between them.
Book a call →The directory stays free. There is nothing gated behind this.