Choose a surface

Person research

Choose POST /v1/person when you have one person to research and need a reviewed report, professional history, source links, and field-level provenance.

Good examples:

• Confirm a prospect's identity and current role before outreach.
• Gather evidence-backed interests and public presence for personalization.

Datasets

Choose Datasets when the deliverable is a persistent, criteria-verified list built over multiple steps. Set your criteria and build a dataset of everyone who matches; save it, refine it, and export it whenever you need. Datasets run asynchronously, verify every criterion, and emit progress. They are in preview and available to API keys with the people:search scope; imports and enrichment columns are workspace-only for now.

Search

Choose POST /v1/search to find people with a single query: a fast one-shot list of up to 150 people. It is useful for interactive autocomplete, small cohorts, and low-latency agent tools.

Profiles

Choose Profiles when you already know the person and need their full public profile from LinkedIn, Instagram, GitHub, Reddit, and more: work history, bio, activity, and links.

Contacts

Choose Contacts when you need the details to reach someone: verified work and personal emails and phone numbers for a known identity.

Monitors

Choose Monitors (/v1/monitors, in the OpenAPI document) to get notified when people or lists change: job changes, profile updates, new posts, or new people matching your criteria.

CLI

Choose the CLI for terminal exploration, local scripts, manual QA, and smoke tests.

MCP

Choose the hosted MCP server when people research should be available as native tools inside ChatGPT, Claude, or another MCP client. Add https://api.ploid.com/mcp; Ploid handles sign-in and scoped workspace access.