For Agents
Enrich person and company records, search a 3+ billion profile dataset with SQL-like queries, and resolve IPs to companies. Supports enrichment by email, phone, name, LinkedIn, and domain.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the People Data Labs API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with People Data Labs API.
Enrich person profiles from email, phone, LinkedIn URL, or name plus company combination
Search the full person dataset using SQL-like queries with boolean filters on 100+ fields
Look up company firmographics including size, industry, funding, and tech stack by domain
GET STARTED
Use for: I need to enrich a person's profile from their LinkedIn URL, Search for all VPs of Engineering at Series B companies in San Francisco, Find the company associated with a specific IP address, I want to look up company details by domain name
Not supported: Does not handle email sending, CRM workflow automation, or marketing campaign management — use for person and company data enrichment and search only.
Enrich, search, and retrieve person and company records from a dataset of over 3 billion profiles. The API supports person enrichment by name, email, phone, or social profile, company enrichment by domain, and SQL-like search queries across the full dataset. Additional endpoints handle IP-to-company resolution, job title standardisation, skill normalization, and autocomplete for fields like companies, schools, and locations across 21 operations.
Resolve IP addresses to the company operating from that network
Standardise free-text job titles to canonical titles and seniority levels
Normalize skill descriptions into structured skill taxonomy entries
Autocomplete partial inputs for companies, schools, locations, and job titles
Patterns agents use People Data Labs API for, with concrete tasks.
★ AI Agent Lead Enrichment via Jentic
AI agents building prospect lists can search People Data Labs through Jentic to enrich sparse lead data into full profiles. Given an email or LinkedIn URL, the agent retrieves job title, company, seniority, location, skills, and social links — enabling automated lead scoring and outreach personalisation without manual research across multiple platforms.
Search Jentic for 'enrich person by email', load the People Data Labs /v5/person/enrich schema, and submit a GET with email 'jane.smith@acme.com' to retrieve her full professional profile
Targeted Prospect Search with SQL Queries
Sales and recruiting teams find ideal candidates or accounts by querying the full People Data Labs dataset using SQL-like syntax. Filter by job title, company size, location, industry, skills, and seniority across 3+ billion records. Results include full enriched profiles ready for outreach, with pagination supporting bulk list builds.
POST to /v5/person/search with SQL query "SELECT * FROM person WHERE job_title='CTO' AND location_country='united states' AND job_company_size='501-1000'" and retrieve the first 10 results
IP-to-Company Resolution for Website Visitors
Marketing and sales platforms identify anonymous website visitors by resolving their IP addresses to company records. The /v5/ip/enrich endpoint maps an IP to the company operating from that network, returning firmographic data that powers account-based marketing triggers and personalised website experiences.
GET /v5/ip/enrich with ip='203.0.113.42' and retrieve the company name, domain, industry, and employee count associated with that IP address
Company Enrichment for Account-Based Sales
Account executives research target companies by passing a domain to the company enrichment endpoint. The API returns industry, employee count, revenue estimates, tech stack, funding history, and headquarters location, giving reps the context they need to personalise outreach and qualify accounts.
GET /v5/company/enrich with website='stripe.com' and retrieve the company name, industry, employee count, funding total, and headquarters location
21 endpoints — enrich, search, and retrieve person and company records from a dataset of over 3 billion profiles.
METHOD
PATH
DESCRIPTION
/v5/person/enrich
Enrich a person record from identifiers
/v5/person/search
Search persons with SQL-like queries
/v5/person/identify
Identify a person from partial data
/v5/company/enrich
Enrich company data by domain or name
/v5/company/search
Search companies with SQL-like queries
/v5/ip/enrich
Resolve an IP address to a company
/v5/autocomplete
Autocomplete partial field values
/v5/job_title/enrich
Standardise a free-text job title
/v5/person/enrich
Enrich a person record from identifiers
/v5/person/search
Search persons with SQL-like queries
/v5/person/identify
Identify a person from partial data
/v5/company/enrich
Enrich company data by domain or name
/v5/company/search
Search companies with SQL-like queries
Three things that make agents converge on Jentic-routed access.
Credential isolation
People Data Labs API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access via the X-API-Key header — raw keys never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'find people by job title and location') and Jentic returns matching PDL operations with input schemas, so the agent can construct SQL-like queries without reading documentation.
Time to first call
Direct PDL integration: 3-5 days for auth, query syntax, pagination, and error handling. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using People Data Labs API through Jentic.
What authentication does the People Data Labs API use?
The API uses an API key passed in the X-API-Key header on every request. Through Jentic, this key is stored encrypted in the credential vault and injected automatically — agents authenticate without handling raw keys.
Can I search for people by job title and location with the People Data Labs API?
Yes. The /v5/person/search endpoint accepts SQL-like queries. For example: SELECT * FROM person WHERE job_title='Data Engineer' AND location_country='united states'. You can filter on 100+ fields including skills, company size, industry, and seniority.
What are the rate limits for the People Data Labs API?
Rate limits vary by plan. The free tier allows 100 person enrichments per month. Paid plans offer higher throughput with per-minute rate limits documented in your account dashboard. Bulk endpoints like /v5/person/retrieve/bulk support up to 100 records per request.
How do I enrich a person through Jentic?
Install the SDK with pip install jentic and search for 'enrich person from email'. Jentic returns the People Data Labs /v5/person/enrich operation schema. Pass identifiers like email, LinkedIn URL, or name+company as query parameters and Jentic handles auth and execution.
Can I resolve an IP address to a company using this API?
Yes. The /v5/ip/enrich endpoint accepts an IP address and returns the company operating from that network, including company name, domain, industry, and size. This is useful for identifying anonymous website visitors at the account level.
What is the difference between person/enrich and person/identify?
The /v5/person/enrich endpoint requires enough identifiers to match a single record and returns a full profile. The /v5/person/identify endpoint works with less data and returns multiple candidate matches ranked by confidence score, useful when you have sparse input data.
/v5/ip/enrich
Resolve an IP address to a company
/v5/autocomplete
Autocomplete partial field values
/v5/job_title/enrich
Standardise a free-text job title