> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atako.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Prospeo

> Connect Prospeo to your Atako agents — 6 read and 0 write actions.

Let your agents enrich and search B2B contacts and companies with Prospeo: find a person's verified work e-mail (and mobile) from a name and a company or a LinkedIn URL, enrich a company, search people and companies with filters, look up the exact filter values, and read the credit balance.

## Connection

* **Authentication**: API key (Prospeo API key).

> [!NOTE]
>
> In Prospeo (app.prospeo.io): left sidebar → "Enrich" → "API" (app.prospeo.io/api) → "Create API Key" → copy the key. Enrichments and searches spend credits (see prospeo.io for the plans); the credit balance and the filter lookups are free.
>
> See [Prospeo's documentation](https://prospeo.io/api-docs).

## Read actions (6)

| Action | Description |
| - | - |
| `enrich_company` | Lookup ONE company and return its profile (industry, size, location, revenue range, links, technologies…) (a read that spends credits). Spends 1 credit per matched company, 0 if no match or if enriched in the last 90 days. Arguments, at least ONE (all strings): company\_website (root domain such as "intercom.com", preferred), company\_linkedin\_url, company\_id (from a previous result), company\_name (ambiguous, avoid alone). |
| `enrich_person` | Lookup ONE person and return the profile, company and work e-mail (a read that spends credits). Spends 1 credit per e-mail found and 10 credits when a mobile is requested and found (the e-mail is then included); 0 credit if no match or if the record was enriched in the last 90 days. A person that cannot be matched answers HTTP 400 error\_code NO\_MATCH (also when only\_verified\_email or only\_verified\_mobile is set and the record has none); INVALID\_DATAPOINTS if the minimum is not met. Arguments, at least ONE of these combinations: first\_name + last\_name + one of (company\_name, company\_website, company\_linkedin\_url); full\_name + one of (company\_name, company\_website, company\_linkedin\_url); linkedin\_url; email; person\_id (the id returned by search\_person). All strings. Prefer company\_website (root domain such as "intercom.com") over company\_name alone. Options: only\_verified\_email (boolean, default false: answer only if the e-mail is VERIFIED), enrich\_mobile (boolean, default false: also reveal the mobile, costs 10 credits when found), only\_verified\_mobile (boolean, default false: answer only if a mobile exists, implies enrich\_mobile). |
| `get_account_information` | Get the account information: current plan, remaining and used credits, team members, next quota renewal date (a read, free). No argument. |
| `search_company` | Search companies matching filters, 25 results per page, each with a company object (a read that spends credits). Spends 1 credit per request that returns at least one result (25 results per page), 0 if nothing matches or if the same page was already paid in the last 30 days. Arguments: filters (object, REQUIRED), page (integer 1 to 1000, default 1; read pagination.total\_page in the answer). Filters (keys of the filters object; at least one positive filter is required, an exclude-only search is refused; send values exactly as the Prospeo docs and search\_suggestions give them). Company filters: company \{ names \| websites \| company\_oids: \{ include?: string\[], exclude?: string\[] } } (websites are root domains such as "stripe.com", no www; company\_oids is refused here: use names or websites), company\_location\_search \{ include?, exclude? } (values copied from search\_suggestions with location\_search), company\_headcount\_range (array of 1-10 \| 11-20 \| 21-50 \| 51-100 \| 101-200 \| 201-500 \| 501-1000 \| 1001-2000 \| 2001-5000 \| 5001-10000 \| 10000+), company\_headcount\_custom \{ min?: integer, max?: integer } (not with the range), company\_industry \{ include?, exclude? } (exact industry names, e.g. "Software Development"), company\_keywords \{ include: string\[] (3 to 100 chars), exclude?, include\_all?: boolean }, company\_technology \{ include?, exclude? } (max 20, exact technology names), company\_revenue \{ min?, max?, include\_unknown\_revenue?: boolean } (min/max among \<100K \| 100K \| 500K \| 1M \| 5M \| 10M \| 25M \| 50M \| 100M \| 250M \| 500M \| 1B \| 5B \| 10B+; paid plan), company\_founded \{ min?: year, max?: year, include\_unknown\_founded?: boolean }, company\_funding \{ stage?: string\[], funding\_date?: 30\|60\|90\|180\|270\|365 (days), investors?: string\[] } (paid plan), company\_job\_posting\_hiring\_for \{ include?, exclude?, match\_type?: "contains" \| "exact" } (paid plan). Any other filter of the Prospeo "Filters Documentation" page (NAICS/SIC codes, headcount growth, news, intent, website traffic, lookalike, ICP, attributes, key execs…) is accepted as is: pass its exact JSON form from that page; some need a paid plan (error PLAN\_REQUIRED). Example: \{ "filters": \{ "company\_industry": \{ "include": \["Software Development"] }, "company\_headcount\_range": \["51-100", "101-200"], "company\_location\_search": \{ "include": \["France"] } } }. Errors: INVALID\_FILTERS (see filter\_error), PLAN\_REQUIRED, NO\_RESULTS. |
| `search_person` | Search people matching filters, 25 results per page, each with a person and its current company; e-mails and mobiles are NOT returned (pass a person\_id to enrich\_person to reveal them) (a read that spends credits). Spends 1 credit per request that returns at least one result (25 results per page), 0 if nothing matches or if the same page was already paid in the last 30 days. Arguments: filters (object, REQUIRED), page (integer 1 to 1000, default 1; read pagination.total\_page in the answer). Filters (keys of the filters object; at least one positive filter is required, an exclude-only search is refused; send values exactly as the Prospeo docs and search\_suggestions give them). Company filters: company \{ names \| websites \| company\_oids: \{ include?: string\[], exclude?: string\[] } } (websites are root domains such as "stripe.com", no www; company\_oids only on search\_person), company\_location\_search \{ include?, exclude? } (values copied from search\_suggestions with location\_search), company\_headcount\_range (array of 1-10 \| 11-20 \| 21-50 \| 51-100 \| 101-200 \| 201-500 \| 501-1000 \| 1001-2000 \| 2001-5000 \| 5001-10000 \| 10000+), company\_headcount\_custom \{ min?: integer, max?: integer } (not with the range), company\_industry \{ include?, exclude? } (exact industry names, e.g. "Software Development"), company\_keywords \{ include: string\[] (3 to 100 chars), exclude?, include\_all?: boolean }, company\_technology \{ include?, exclude? } (max 20, exact technology names), company\_revenue \{ min?, max?, include\_unknown\_revenue?: boolean } (min/max among \<100K \| 100K \| 500K \| 1M \| 5M \| 10M \| 25M \| 50M \| 100M \| 250M \| 500M \| 1B \| 5B \| 10B+; paid plan), company\_founded \{ min?: year, max?: year, include\_unknown\_founded?: boolean }, company\_funding \{ stage?: string\[], funding\_date?: 30\|60\|90\|180\|270\|365 (days), investors?: string\[] } (paid plan), company\_job\_posting\_hiring\_for \{ include?, exclude?, match\_type?: "contains" \| "exact" } (paid plan). Any other filter of the Prospeo "Filters Documentation" page (NAICS/SIC codes, headcount growth, news, intent, website traffic, lookalike, ICP, attributes, key execs…) is accepted as is: pass its exact JSON form from that page; some need a paid plan (error PLAN\_REQUIRED). Person filters: person\_search \{ include?, exclude?: string\[] (names, company names or domains), match\_mode?: "SMART" \| "STRICT" }, person\_job\_title \{ include?, exclude?: string\[] (max 100), match\_mode: "CONTAINS" \| "EXACT" \| "SIMILAR" } or \{ boolean\_search: string, e.g. "(CEO OR CTO) AND !intern" } (not both), person\_seniority \{ include? \| exclude?: array of C-Suite \| Director \| Entry \| Founder/Owner \| Head \| Intern \| Manager \| Partner \| Senior \| Vice President } (not both), person\_department \{ include? \| exclude?: string\[] } (not both; e.g. "Sales", "Marketing", "Engineering & Technical", "Finance", "Operations", "Product", "Human Resources", "C-Suite"), person\_location\_search \{ include?, exclude? } (values copied from search\_suggestions with location\_search), person\_contact\_details \{ email?: \["VERIFIED"], mobile?: \["VERIFIED" \| "UNAVAILABLE"], operator?: "OR" \| "AND", hide\_people\_with\_details\_already\_revealed?: boolean }, person\_year\_of\_experience \{ min?: 0-60, max?: 1-60 }, person\_time\_in\_current\_role / person\_time\_in\_current\_company \{ min?, max? } (months), person\_name\_or\_job\_title (string), max\_person\_per\_company (integer 1 to 100). Example: \{ "filters": \{ "person\_job\_title": \{ "include": \["CTO"], "match\_mode": "CONTAINS" }, "company\_headcount\_range": \["51-100"], "company\_location\_search": \{ "include": \["France"] }, "max\_person\_per\_company": 1 } }. Errors: INVALID\_FILTERS (see filter\_error), PLAN\_REQUIRED, NO\_RESULTS. |
| `search_suggestions` | Lookup the exact values accepted by the search filters (a read, free; 15 calls per second). Pass EXACTLY ONE argument, a string of at least 2 characters, depending on the filter to fill: location\_search (values for person\_location\_search and company\_location\_search, copy them unchanged), job\_title\_search, technology\_search (company\_technology), industry\_search (company\_industry), naics\_search or sic\_search (a code prefix or a label), or a company field: company\_operating\_languages\_search, company\_google\_discovery\_search, company\_key\_customers\_search, company\_integrations\_search, company\_products\_services\_products\_search, company\_products\_services\_services\_search, company\_icp\_titles\_search, company\_icp\_industries\_search, company\_icp\_geographic\_markets\_search, company\_icp\_other\_departments\_search, company\_awards\_search, company\_awards\_compliance\_search, company\_headcount\_by\_location\_search, company\_funding\_investors\_search, company\_funding\_accelerator\_search, company\_website\_traffic\_countries\_search. The answer carries the list under the matching \*\_suggestions key. |

## Write actions (0)

This connector is read-only — it exposes no write actions.

## Permissions

Every action above must be explicitly granted to an agent before it can be used. See [Permissions](https://docs.atako.ai/integrations/permissions.md) for the grant model and [Security](https://docs.atako.ai/integrations/security.md) for how credentials are protected.

***

*Last reviewed against the provider API: October 2026.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.