canonical: https://jentic.com/apis/listplus.ai/listplus

# ListPlus agent API

The ListPlus agent API checks B2B contact and company records for errors, sizes markets, finds people and leads, and fills missing fields such as work email, mobile number, job title, and LinkedIn profile. Its record checks run more than 100 tests covering email-domain typos, role mailboxes, duplicates, and phone codes that do not fit the country, and are free for up to 25 records without a key. Beyond one-off lookups, it works on a workspace's lists: query, add, update, tag, deduplicate, derive columns, set trigger rules, and hand records to a pipeline such as HubSpot, Slack, or lemlist. Every paid action accepts estimate: true to return its price without running, and every response carries options with next steps and their prices.

## For AI agents

Check B2B contact records for errors, find people by name or role, search and count companies, enrich missing emails and phone numbers, verify emails, and manage workspace lists.

## Scope

Does not handle email sending, campaign sequencing, or CRM deal tracking itself. Use for checking, finding, enriching, and organising B2B contact and company records only.

## Capabilities

- Check contact and company records for errors such as email-domain typos, role mailboxes, and near-duplicates with check_records
- Find a person by name and company, LinkedIn URL, work email, or a natural-language query with find_person
- Fill missing email, phone, job_title, linkedin_profile_url, or company fields on records with enrich_records, priced first with estimate
- Verify whether email addresses are deliverable, returning valid, invalid, catch_all, or unknown
- Count companies that match filters such as countries and naics codes, broken down by one dimension
- Search people by job_titles, seniorities, departments, locations, and company_domains, and load matching companies into a list
- Clean a workspace list with check_list and fix_list, then send its records to a HubSpot, Slack, or lemlist pipeline

## Use cases

### AI sales assistant cleaning and enriching a lead list

A sales assistant agent given a pasted CRM export can tell the user what is wrong and what it would cost to fix. Through Jentic the agent searches for 'check contact records for errors', calls check_records on the rows, then calls enrich_records with estimate: true for the missing email and phone fields and relays the price before running it. The agent key is injected by Jentic, and each response's tell_your_user text gives the agent a plain summary to pass on.

Example prompt: POST `/a/v1/check_records` with the user's records, then POST `/a/v1/enrich_records` with fields ['email', 'phone'] and estimate true, report the price, and rerun without estimate once the user approves

### Market sizing before a campaign

Before committing to a segment, a founder wants to know how many companies fit it. count_companies returns the number of companies matching filters such as countries and naics codes for free, and with the by option and a key it breaks the total down by a dimension such as industries, employees, or revenue. search_options returns the exact filter values to use.

Example prompt: POST `/a/v1/search_options` to get the naics value for apparel manufacturing, then POST `/a/v1/count_companies` with filters countries ['IT'] and naics ['315'] and by 'employees'

### Prospect search and list building

Outbound teams build lists of decision-makers that match a profile. search_people filters by job_titles, seniorities, departments, locations, industries, headcount, and company_domains, with has_email and has_mobile flags, and can write results into a list_id. load_companies does the same for company records, accepts max_credits as a ceiling, and supports estimate for the price first.

Example prompt: POST `/a/v1/search_people` with job_titles ['Head of Marketing'], locations ['Germany'], has_email true, and a list_id, then POST `/a/v1/describe_list` to confirm the records landed

### Email deliverability checks before sending

Sending to bad addresses hurts sender reputation. verify_email checks whether each address is deliverable and labels it valid, invalid, catch_all, or unknown, at 0.3 credits per address according to the spec, with addresses checked in the last 7 days at no charge.

Example prompt: POST `/a/v1/verify_email` with a list of 50 addresses and drop any marked invalid before passing the rest to the sequencer

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/a/v1/check_records` | Check records for errors |
| POST | `/a/v1/find_person` | Find a person |
| POST | `/a/v1/enrich_records` | Enrich records with missing fields |
| POST | `/a/v1/verify_email` | Verify email deliverability |
| POST | `/a/v1/search_people` | Search people by role and company |
| POST | `/a/v1/count_companies` | Count companies matching filters |
| POST | `/a/v1/get_job` | Get job status |
| POST | `/a/v1/send_to_pipeline` | Send records to a pipeline |

## Key resources

- **Record checks** — Free error checks on contact and company records across categories such as email, phone, duplicates, and compliance
- **People and companies** — Find a person, search people, count companies, load companies, and search filter options
- **Enrichment** — Fill missing email, phone, job title, LinkedIn, and company fields, verify emails, and poll enrichment jobs
- **Lists** — Create lists, query, add, update, mark, copy, check, fix, and derive columns on workspace records
- **Rules and pipelines** — Trigger rules on list events and handover of records to workspace pipelines

## 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:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 82 / 100
  - Developer Experience & Jentic Compatibility: 64 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 54 / 100
- **View full report:** https://jentic.com/apis/listplus.ai/listplus/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 <openapi-url>
```

## Why Jentic

- **Setup:** Wiring ListPlus by hand means handling a bearer agent key, tracking which operations run anonymously and which need the key, calling estimate before paid actions, and polling get_job for long runs. Through Jentic you install once, import ListPlus from the API Directory, store the agent key once, and your agent calls it.
- **Permission scoping:** ListPlus exposes each action as its own POST path and carries the list_id and records in the request body, so rules bound which operations your agent may call, not which list it works on. You choose the operations it may call, so credit-spending or destructive ones like enrich_records or remove_column are not included unless you add them.
- **Credential handling:** Your ListPlus agent 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 'check contacts for errors' or 'find a person at a company', and Jentic returns the matching ListPlus operation with its input schema so the agent calls the right action without reading the manual.

## Related APIs

- **Apollo.io API** — B2B contact database with people search, enrichment, and sequencing.
- **Hunter API** — Find and verify professional email addresses by domain.
- **NeverBounce API** — Dedicated bulk email verification.
- **HubSpot CRM Contacts** — The CRM where cleaned and enriched contacts often end up.

## FAQ

### What authentication does the ListPlus agent API use?

The OpenAPI spec declares agentKey, an HTTP bearer scheme that carries a workspace agent key beginning with lpk_, issued from the agents page of a ListPlus workspace. A few operations also accept anonymous calls, including what_can_you_do, search_options, count_companies, and check_records for up to 25 records, while enrichment, people search, email verification, and list work need the key.

### How much does enrichment cost with the ListPlus agent API?

Per the enrich_records description, filling a work email from a name and company costs about 2.39 credits per record and at most 9, a mobile about 3.84 and at most 12, and a job title about 1.41 and at most 13.5, charged per hit for email and phone. verify_email costs 0.3 credits per address. Sending estimate: true on a paid action returns its exact price without running it.

### What are the rate limits for the ListPlus agent API?

The OpenAPI spec notes that find_person is rate-limited but does not state numeric limits. Check the ListPlus agent manual at https://listplus.ai/a for current limits.

### Is there a ListPlus MCP server?

You don't need an MCP server to give your agent ListPlus. Jentic connects it directly from the API Directory: import it, store your agent key once, and your agent calls the check, find, and enrich operations it needs, discovered on demand rather than preloaded into its context.

### Can I limit what my agent is allowed to do with ListPlus?

Yes. For example, write a rule that allows only check_records, count_companies, and find_person, so the agent can audit records, size markets, and look people up but cannot spend credits through enrich_records or verify_email, or change a list with update_records. Every call it makes is logged.

### How do I enrich records through Jentic?

Add ListPlus to your Jentic One instance from the directory and store your lpk_ agent key. Your agent searches for 'fill missing work emails', loads the enrich_records operation, and posts the records with fields such as email and phone, first with estimate: true to get the price, then polls get_job with the returned job_id for larger runs. To run it on your own infrastructure, install Jentic One from its GitHub repo.
