canonical: https://jentic.com/apis/ploid.com/ploid # Ploid Public API 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. ## For AI 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. ## Scope Does not handle email sending, CRM record storage, or identity verification for compliance checks. Use for finding, resolving, enriching, and monitoring people only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Search** — Natural-language people search in several modes, plus basic candidate search by name, company, location, and title. - **People** — Resolve one person to a person_id, build deep profiles as pollable runs, and enrich contact fields. - **Monitors** — Compile, create, update, pause, run, and delete scheduled social monitors, and list their runs and emitted items. - **LinkedIn and socials** — LinkedIn profiles, posts, comments, companies, and company posts, plus public profiles on other platforms. - **Harness** — Load Ploid memory context for another agent runtime and run bounded tool-calling model requests. - **Account** — ACU balance, API key budget, usage, profile, and revoking the current key. ## AI readiness 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. - **Score:** 58 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 51 / 100 - Developer Experience & Jentic Compatibility: 65 / 100 - AI-Readiness & Agent Experience: 44 / 100 - Agent Usability: 94 / 100 - Security: 55 / 100 - AI Discoverability: 65 / 100 - **View full report:** https://jentic.com/apis/ploid.com/ploid/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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 - **People Data Labs** — People Data Labs serves a large person and company dataset by query; Ploid adds identity resolution, evidence-backed deep profiles, and social monitors. - **Apollo** — Apollo combines contact data with sales engagement sequences; Ploid focuses on finding, resolving, and enriching people. - **Clearbit** — Clearbit enriches people and companies from an email or domain; Ploid resolves people from names and clues and monitors social activity. - **Attio** — Attio is a CRM; Ploid supplies the enriched people and contact fields to store in it. ## FAQ ### 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.