Install Jentic One Beta

Connect the LinkedIn People Search API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LinkedIn People Search 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Falphaosint.com%2Falphaosint" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Falphaosint.com%2Falphaosint" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with LinkedIn People Search API.

Search LinkedIn for people by first and last name, job title, employer, school, or location

Return structured public profiles with headline, current employer, profile URL, and photo

Enrich each match with about text, full work history, education, and follower counts

Cap a run with maxResults to control how many people and how much cost each search returns

GET STARTED

Start building with LinkedIn People Search API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use LinkedIn People Search API for, with concrete tasks.

★ Agent-Driven LinkedIn Prospecting

An AI agent researching a sales list calls the LinkedIn People Search API through Jentic to turn a name, company, or job title into structured public profile data: profile URL, headline, current employer, work history, and education. The agent passes search fields such as firstName, lastName, company, and jobTitle, sets maxResults to bound the run, and reads back a clean JSON list without logging into LinkedIn or handling a session cookie.

Search for people with jobTitle 'Software Engineer' at company 'Microsoft' in location 'San Francisco' with maxResults 25 and return each profile URL and headline

Recruiter Candidate Sourcing

A recruiting team sources candidates by requiring a job title, employer, and school, then pulls each person's public work history and education to build a shortlist. The LinkedIn People Search API matches people whose public profile mentions the given company, current or past, and the enrichProfiles option adds about text, languages, and connection counts for deeper screening. Results come back as structured JSON, so there is no manual profile scraping.

Find people with jobTitle 'Data Scientist', school 'Stanford University', and enrichProfiles true, then return their work history and education

Contact Enrichment From a Name

Given only a first and last name, the LinkedIn People Search API returns a matching public profile with the person's current employer, headline, and profile URL, enriching a thin CRM record with verified role and company data. Turning enrichProfiles off keeps a run fast and cheap when only the headline and employer are needed, while turning it on adds the full history. The exact-phrase name match keeps results tight to the person you asked for.

Look up the person 'Jane Doe' with enrichProfiles false and return their current employer, headline, and profile URL

Key Endpoints

3 endpoints — the linkedin people search api finds people on linkedin by name, job title, company, school, or location and returns their public profile data as structured json, including profile url, headline, current employer, about text, work history, education, and follower count.

METHOD

PATH

DESCRIPTION

POST

/acts/johnvc~linkedin-people-search-api/run-sync-get-dataset-items

Run the search and return the matched people as dataset items

POST

/acts/johnvc~linkedin-people-search-api/run-sync

Run the search and return the output from the key-value store

POST

/acts/johnvc~linkedin-people-search-api/runs

Start a search run and return information about the initiated run

POST

/acts/johnvc~linkedin-people-search-api/run-sync-get-dataset-items

Run the search and return the matched people as dataset items

POST

/acts/johnvc~linkedin-people-search-api/run-sync

Run the search and return the output from the key-value store

POST

/acts/johnvc~linkedin-people-search-api/runs

Start a search run and return information about the initiated run

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the LinkedIn People Search API by hand means getting an Apify token, building the actor input body, and choosing between the synchronous dataset endpoint and a plain run you then have to poll. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.

Permission scoping

The actor and its run operations live in the URL path (/acts/johnvc~linkedin-people-search-api/...), so a rule can limit your agent to just these search endpoints and nothing else on the Apify host. The search terms travel in the request body, so rules bound which operations the agent may call, not which names it may search for.

Credential isolation

Your Apify token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find a person on LinkedIn' or 'look up a profile by name', and Jentic returns the matching LinkedIn People Search operation with its input schema so the agent fills in fields like firstName and company without reading the actor docs.

FAQs

Specific to using LinkedIn People Search API through Jentic.

What authentication does the LinkedIn People Search API use?

The LinkedIn People Search API runs on Apify and authenticates with an Apify API token passed as the `token` query parameter on each run request, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's prompt or logs.

Can I search for people by company and job title with the LinkedIn People Search API?

Yes. The search accepts firstName, lastName, keywords, jobTitle, company, school, and location fields, and returns only people whose public profile or search snippet matches the ones you set. Setting enrichProfiles to true adds about text, work history, education, and follower counts to each result, while leaving it off returns just the profile URL, name, headline, and current employer.

What are the rate limits for the LinkedIn People Search API?

The OpenAPI spec does not specify rate limits. The API runs as an Apify actor, so run concurrency and monthly usage follow your Apify account plan; see the Apify platform documentation at https://docs.apify.com for current limits.

How do I find a LinkedIn profile by name through Jentic?

Search Jentic with a query like 'find people on LinkedIn by name', add the LinkedIn People Search API from the directory, and store your Apify token once. Your agent then calls the synchronous run operation with firstName, lastName, and any filters such as company or location, and reads back the matched profiles as dataset items in JSON. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the LinkedIn People Search API?

Yes. Write a rule that allows only the search run operations under the /acts/johnvc~linkedin-people-search-api path, so the agent can run people searches and read results but cannot reach any other actor or dataset on the Apify host, and every call it makes is logged. Because the search terms ride in the request body, scoping controls which operations run, not which individuals the agent may look up.

Is there a LinkedIn People Search API MCP server?

You don't need an MCP server to give your agent the LinkedIn People Search API. Jentic connects it directly from the API Directory: import it, store your Apify token once, and your agent calls the search operations on demand without loading another server's tool definitions into its context.

Alphaosint LinkedIn People Search API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentContact EnrichmentapiKey3 EndpointsREST

For Agents

Search LinkedIn for people by name, job title, company, school, or location and get structured public profiles with work history, education, and current employer. Returns JSON without any LinkedIn login or session cookie.

Use for: Find all software engineers at a named company in a given city, Search for a person by full name and return their LinkedIn profile, Get the work history and education for a matched LinkedIn profile, I want to look up people who studied at a specific university

Not supported: Does not handle messaging, connection requests, or company-page data. Use for public LinkedIn people search and profile enrichment only.

The LinkedIn People Search API finds people on LinkedIn by name, job title, company, school, or location and returns their public profile data as structured JSON, including profile URL, headline, current employer, about text, work history, education, and follower count. It runs as an Apify actor, so a single search request accepts rich filters and an enrichProfiles flag that controls how much profile detail each match carries. No LinkedIn login, session cookie, or account is required.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

53%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

18%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1

50%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the LinkedIn People Search API to your agent

Capabilities

Start building with LinkedIn People Search API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Alphaosint LinkedIn People Search API

Jentic AI Readiness Score

LinkedIn People Search API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness