Install Jentic One Beta

Connect the Prospeo API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Prospeo 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.

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%2Fprospeo.io%2Fprospeo" | sh

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%2Fprospeo.io%2Fprospeo" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Prospeo API.

Enrich a person from datapoints such as first_name, last_name, company_website, linkedin_url, or email

Return only verified emails with only_verified_email, and add a mobile number with enrich_mobile

Enrich a company from its company_website, company_linkedin_url, or company_name

Enrich up to 50 people or 50 companies in one bulk request

Search people or companies with a filters object, 25 results per page

GET STARTED

Start building with Prospeo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Prospeo API for, with concrete tasks.

★ Agent-Driven Lead Enrichment

An AI agent connected through Jentic takes a name and company from a CRM record or a chat message, enriches the person with only_verified_email set so it only returns deliverable addresses, and adds a mobile number when enrich_mobile is set. Before a large run it reads the account's remaining credits, so it can tell the user when the balance is too low.

Enrich a person with first_name Jane, last_name Doe, and company_website acme.com, with only_verified_email true and enrich_mobile true, after checking remaining credits

Bulk List Enrichment

Sales teams import event attendee lists or CSV exports with names and companies but no emails. The bulk person enrichment operation takes up to 50 records per request, each carrying its own identifier so responses can be matched back to the source rows, which keeps large list jobs to a manageable number of calls.

Send 50 person records with unique identifiers to the bulk enrich person operation and map the returned emails back to the source rows

Account-Based Prospect Search

A rep builds a target list by first resolving valid filter values with the suggestions operation, such as a job title or a technology, then searching people with a filters object for the right seniority, location, and industry. Search results do not carry email or mobile data, so the rep enriches only the people worth contacting.

Get job title suggestions for 'head of sales', search people with that job title in Germany, then enrich the top three results

Company Firmographic Lookup

Before routing an inbound lead, a workflow enriches the company from its website or LinkedIn URL to get firmographic data, and uses company search with filters to find lookalike accounts. Matching on a website or LinkedIn URL is preferred because matching by name alone is discouraged in the spec.

Enrich the company with company_website stripe.com and return its firmographic fields

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for prospeo api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/enrich-person

Enrich a person

POST

/bulk-enrich-person

Enrich up to 50 people

POST

/enrich-company

Enrich a company

POST

/bulk-enrich-company

Enrich up to 50 companies

POST

/search-person

Search people with filters

POST

/search-company

Search companies with filters

POST

/search-suggestions

Get valid filter values

GET

/account-information

Read plan and credit usage

POST

/enrich-person

Enrich a person

POST

/bulk-enrich-person

Enrich up to 50 people

POST

/enrich-company

Enrich a company

POST

/bulk-enrich-company

Enrich up to 50 companies

POST

/search-person

Search people with filters

POST

/search-company

Search companies with filters

POST

/search-suggestions

Get valid filter values

GET

/account-information

Read plan and credit usage

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Prospeo by hand means sending the `X-KEY` header, batching records into bulk requests of up to 50 with your own identifiers, and paging searches at 25 results per page. Through Jentic you install once, import Prospeo from the API Directory, store the key once, and your agent calls it.

Permission scoping

Prospeo carries every lookup target in the request body, so a rule bounds which operations your agent may call rather than which person or company. You choose the operations it may call, so credit-heavy bulk enrichment is not included unless you add it.

Credential isolation

Your Prospeo 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 person's work email' or 'search companies by industry', and Jentic returns the matching Prospeo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Prospeo API through Jentic.

Why is there no official OpenAPI spec for Prospeo API?

Prospeo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Prospeo API via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What authentication does the Prospeo API use?

The Prospeo API authenticates with an API key from the Prospeo dashboard, sent in the `X-KEY` header under the ApiKeyAuth scheme in its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt, logs, or context.

What are the rate limits for the Prospeo API?

The OpenAPI spec states one numeric limit: the search suggestions operation is rate limited to 15 requests per second per account. It does not give limits for the other operations; check https://prospeo.io/api-docs for current limits.

Does a Prospeo search return emails?

No. Person search returns up to 25 results per page across up to 1000 pages, but email and mobile data require a separate enrich person call. Search first to find the right people, then enrich only the ones you want to contact.

Is there a Prospeo MCP server?

You don't need an MCP server to give your agent Prospeo. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, finding the enrich and search operations on demand.

Can I limit what my agent is allowed to do with the Prospeo API?

Yes. For example, write a rule that allows only the enrich person and account information operations, so the agent can look up single contacts and check the credit balance while the bulk enrichment operations, which spend credits faster, stay out of reach. Every call it makes is logged.

Prospeo API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticData EnrichmentContact EnrichmentapiKey8 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Enrich a person or company with verified emails, mobile numbers, and firmographics, search Prospeo's contact and company databases with filters, and check remaining credits.

Use for: Find the work email for Jane Doe at acme.com, Get a verified email and mobile number from this LinkedIn profile, Enrich these 40 leads in one request, Search for VP of Sales contacts at SaaS companies in Germany

Not supported: Does not send email, run outreach sequences, or store CRM records. Use for B2B person and company enrichment and search only.

Jentic publishes the only available OpenAPI specification for Prospeo API, keeping it validated and agent-ready. The Prospeo API enriches people and companies with B2B contact and firmographic data and searches its contact and company databases. It enriches a person from datapoints such as a name and company, a LinkedIn URL, or an email, with options to return only verified emails and to include a mobile number, and enriches a company from its website, LinkedIn URL, or name. Bulk operations take up to 50 records per request, searches use a filters object and return 25 results per page, and a suggestions operation returns valid filter values for locations, job titles, technologies, and industries.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

16%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

83%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Prospeo API to your agent

Capabilities

Start building with Prospeo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Prospeo API

Jentic AI Readiness Score

Prospeo API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness