Ploid Public API
58
AI ReadinessFoundational (C+)58/100
Official vendor OpenAPI document · agent-readyData EnrichmentContact Enrichmentbearer, apiKey32 EndpointsREST
For Agents
Search for people by description, identify one person from a name and a clue, build an evidence-backed profile, and enrich contact fields with confidence and source. Also runs scheduled social monitors and reads LinkedIn profiles, posts, and companies.
Use for: I need to find the head of engineering at a fintech startup in Berlin, Identify the right Jane Doe who works at Acme, Get a work email and phone number for this LinkedIn profile, Build a full profile on a sales prospect before a call
Not supported: Does not handle email sending, CRM record storage, or identity verification for compliance checks. Use for finding, resolving, enriching, and monitoring people only.
The Ploid Public API finds, identifies, and enriches people for agent workflows, billed in ACU credits. A search takes a natural-language query with instant, fast, auto, or deep modes and returns matches inline or as a background People Set; resolve identifies one person from a name plus a clue such as company, role, or email and returns a permanent person_id; and the person operation builds an evidence-backed deep profile, returning a run to poll when fresh research is needed. Enrich returns work_email, personal_email, or phone with confidence, source, and last_seen for each field. Scheduled monitors watch LinkedIn, X, Instagram, and TikTok and emit items on each run, and LinkedIn profile, post, comment, and company operations sit alongside account credit and usage reads.
Install Jentic One Beta
Connect the Ploid Public API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ploid Public 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.
1
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%2Fploid.com%2Fploid" | sh2
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%2Fploid.com%2Fploid" | 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.
Capabilities
What an agent can do with Ploid Public API.
Search for people with a natural-language query in instant, fast, auto, or deep mode, inline or as a background People Set with a webhook_url
Identify one person from a name plus a clue such as company, role, location, work_email, or phone, and get a permanent person_id
Build an evidence-backed deep person profile, polling the returned run id and cancelling a run that is no longer needed
Enrich a person with work_email, personal_email, or phone, each reported as found, not_found, or unavailable with confidence, source, and last_seen
Create, pause, run, and read scheduled monitors over LinkedIn, X, Instagram, and TikTok, and list the items each run emits
Read LinkedIn profiles, recent posts, profile comments, companies, and company posts, and resolve public profiles on platforms such as GitHub or YouTube
Check the account's ACU balance, API key budget, and usage before running paid operations
Use Cases
Patterns agents use Ploid Public API for, with concrete tasks.
★ Agent-Driven Prospect Research via Jentic
A sales or recruiting agent given a name and a company needs to be sure it has the right person before spending credits on a deep profile. Through Jentic it calls resolve with the name and company, takes the returned person_id, and only then calls the person operation for an evidence-backed profile, polling the run until it completes and stopping when the identity comes back unsure.
Resolve 'Jane Doe' at company 'Acme Corp' with role 'VP Sales', then request a deep profile with the returned person_id, poll getPersonRun until done, and summarise her current role and recent activity
Contact Enrichment for Outreach
Teams enriching a lead list send a LinkedIn URL, a person_id, or a name plus company domain to the enrich operation and ask for work_email, personal_email, or phone. Each field is reported as found, not_found, or unavailable with its confidence, source, and last_seen date, and the response states what was billed, so not-found fields are visible rather than silently missing.
Enrich a LinkedIn profile URL requesting work_email and phone, and report each field's status and confidence
Natural-Language People Search
Recruiters and founders describe who they want in plain language and let the search operation return matches. Instant and fast modes return indexed candidates quickly, while auto and deep research the query and filters and exclude uncertain candidates, and larger requests run as a background People Set that can notify a webhook_url when ready.
Search for 'senior Rust engineers in Lisbon who have worked at a payments company' in auto mode with num_results 25, and list each match with its verification reference
Social Monitoring for Mentions and Activity
Marketing and sales teams track what people and companies post by creating a monitor with a query and a schedule. The compileMonitor operation previews the plan and output schema first, each scheduled run fetches targets across LinkedIn, X, Instagram, and TikTok, and listMonitorItems returns what each run emitted for review or a webhook.
Compile and then create a monitor that checks LinkedIn and X daily for posts mentioning 'Acme Payments', then list the items from its latest run
Key Endpoints
32 endpoints — the ploid public api finds, identifies, and enriches people for agent workflows, billed in acu credits.
METHOD
PATH
DESCRIPTION
POST
/v1/search
Search people by natural-language query
POST
/v1/resolve
Identify one person from a name and a clue
POST
/v1/person
Get an evidence-backed person record
GET
/v1/person/runs/{id}
Poll a deep person run
POST
/v1/enrich
Enrich one person's contact fields
POST
/v1/monitors
Create a social monitor
GET
/v1/linkedin/profile
Fetch a LinkedIn profile
GET
/v1/account/credits
Get account balance and API key budget
POST
/v1/search
Search people by natural-language query
POST
/v1/resolve
Identify one person from a name and a clue
POST
/v1/person
Get an evidence-backed person record
GET
/v1/person/runs/{id}
Poll a deep person run
POST
/v1/enrich
Enrich one person's contact fields
POST
/v1/monitors
Create a social monitor
GET
/v1/linkedin/profile
Fetch a LinkedIn profile
GET
/v1/account/credits
Get account balance and API key budget
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
Ploid Public API
- Foundational (C+)58/100
51
Foundational Compliance65
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience94
Agent Usability55
Security65
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
51
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C-Signals: 4
92%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
10%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
65
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
59%
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.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
19%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
57%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
55
Security
Trust, risk posture, and security compliance.
Grade: CSignals: 1
55%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
65
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
65%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Ploid by hand means choosing between a bearer token and an x-api-key header, holding the right people and agent scopes, sending Idempotency-Key headers to avoid double charges, and polling deep profile runs. Through Jentic you install once, import Ploid from the API Directory, store the key once, and your agent calls it.
Permission scoping
Ploid puts the monitor id in the URL path (/v1/monitors/{id}/...), so a rule can pin your agent to one monitor and its runs. Search, resolve, and enrich take their target in the request body, so for those rules bound which operations the agent may call. You choose the operations it may call, so credit-heavy deep profiles and key revocation are not included unless you add them.
Credential isolation
Your Ploid API key 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 work email for a person' or 'identify a person from a name and company', and Jentic returns the matching Ploid operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Ploid Public API through Jentic.
What authentication does the Ploid Public API use?
The Ploid Public API declares two schemes in its OpenAPI spec: a bearer token in the Authorization header, or an API key in the x-api-key header. Operations also check scopes on the key, such as people:search for search and resolve, people:enrich for enrich and socials, and agent:chat for the harness operations. Downloading the OpenAPI document at /v1/openapi.json is open. Through Jentic the key is stored encrypted on your own instance and injected at call time.
Is there a Ploid MCP server?
You don't need an MCP server to give your agent Ploid. Jentic connects it directly from the API Directory: import Ploid, store your API key once, and your agent can search and enrich people straight away. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.
Can I limit what my agent is allowed to do with the Ploid Public API?
Yes. Write a rule that allows only searchPeopleCandidates and resolvePerson, so the agent can find and identify people but cannot buy deep profiles, create monitors, or revoke your API key, and the calls it makes are logged.
How does Ploid billing work?
Ploid charges in ACU credits, and the spec states the cost on each operation. Basic candidate search costs 1 ACU per completed search, resolve costs 2 ACU when a person is found and nothing when there is no match, and the first successful deep profile costs 25 ACU. Monitors cost 1 ACU to compile or create plus per-target and per-item charges on each run. Sending an Idempotency-Key replays a request without another charge.
What are the rate limits for the Ploid Public API?
The Ploid OpenAPI spec does not publish request rate limits; usage is bounded by your ACU balance and any API key spending cap, which getCredits reports. Check https://ploid.com for current limits.
How do I enrich a contact with the Ploid Public API through Jentic?
Search Jentic for an intent like 'find a work email for a person', import Ploid, and store your API key once. Your agent then calls enrichPerson at /v1/enrich with a LinkedIn URL or a name plus company domain and reads each field's status and confidence. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED