Install Jentic One Beta

Connect the Evaboot Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Evaboot Public 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%2Fevaboot.com%2Fevaboot" | 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%2Fevaboot.com%2Fevaboot" | 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 Evaboot Public API.

Start a lead extraction from a Sales Navigator search URL

Extract a single lead from a profile

List and retrieve extraction jobs by id

Find professional email addresses for leads

Validate email addresses for deliverability

GET STARTED

Start building with Evaboot Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Evaboot Public API for, with concrete tasks.

★ AI Agent Lead Extraction

An AI agent can turn a Sales Navigator search into a structured lead list by starting an extraction job and reading its result. Through Jentic the agent finds the extraction operation by intent and passes the search URL, then polls the job by id, so a sales assistant can build prospect lists without a developer wiring the endpoints by hand.

Start an extraction from a Sales Navigator search URL, then poll the job and return the extracted leads

Email Finding and Verification

A prospecting agent can attach verified email addresses to leads by running the email finder and then validating the results. The API finds professional emails and checks deliverability, so an agent can produce a clean, contactable list and drop addresses that would bounce.

Find an email for a lead, validate it, and return the address only if it is deliverable

Quota-Aware Batch Enrichment

An operations agent can enrich lead lists at scale while staying inside plan limits. The API reports remaining quota and lets an agent start batch email-finder and validation jobs, so a workflow can check the budget before spending it and pace enrichment across runs.

Check the remaining quota, then start an email-finder job only if enough credits are available

Key Endpoints

15 endpoints — the evaboot public api extracts leads from sales navigator and enriches them with verified contact details.

METHOD

PATH

DESCRIPTION

POST

/v1/extractions/url/

Start an extraction from a search URL

POST

/v1/extractions/single/

Extract a single lead from a profile

GET

/v1/extractions/

List extraction jobs

GET

/v1/extractions/{extraction_id}/

Get an extraction job by id

POST

/v1/email-finder/

Start an email-finder job

GET

/v1/email-finder/{job_id}/

Get an email-finder job by id

POST

/v1/email-validation/

Start an email-validation job

GET

/v1/quota/

Check the remaining account quota

POST

/v1/extractions/url/

Start an extraction from a search URL

POST

/v1/extractions/single/

Extract a single lead from a profile

GET

/v1/extractions/

List extraction jobs

GET

/v1/extractions/{extraction_id}/

Get an extraction job by id

POST

/v1/email-finder/

Start an email-finder job

GET

/v1/email-finder/{job_id}/

Get an email-finder job by id

POST

/v1/email-validation/

Start an email-validation job

GET

/v1/quota/

Check the remaining account quota

Why Jentic?

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

Setup

Wiring Evaboot by hand means managing an API token, sending it as a bearer token on every request, and coordinating the start-and-poll pattern for asynchronous jobs. Through Jentic you install once, import Evaboot from the API Directory, store the token once, and your agent calls it.

Permission scoping

You decide which Evaboot operations the agent may use. Allow it to check quota and read results while blocking credit-spending jobs, and because job ids sit in the URL path, a rule can restrict it to specific jobs so it cannot start work you did not approve.

Credential isolation

Your Evaboot API token is stored encrypted by your own Jentic One instance and injected as a bearer token at execution time. It never enters the agent's prompt, logs, or context window.

Intent-based discovery

Agents search Jentic by intent such as 'extract leads' or 'validate an email', and Jentic returns the matching Evaboot operation with its input schema so the agent calls the right endpoint.

FAQs

Specific to using Evaboot Public API through Jentic.

Is there an Evaboot MCP server?

You don't need an MCP server to give your agent the Evaboot Public API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent can extract leads and validate emails. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

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

Yes. You choose which operations the agent may call, so you can allow it to check quota and read extraction results without starting new jobs that spend credits. Because job ids appear in the URL path, a rule can also pin the agent to specific jobs, and every call is logged.

What authentication does the Evaboot Public API use?

The Evaboot Public API authenticates with a bearer token, sent in the Authorization header per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and added to each request at call time, so it never appears in the agent's prompt or logs.

Can my agent find and verify a lead's email with the Evaboot Public API?

Yes. The agent can start an email-finder job for a lead and then run email validation on the result to confirm deliverability. Because jobs run asynchronously, the agent starts a job and reads its outcome by id before returning the address.

What are the rate limits for the Evaboot Public API?

The OpenAPI spec does not specify rate limits, but jobs consume account credits. Check the Evaboot documentation at https://evaboot.com for current quota and request limits, and read the quota operation before starting large batches.

How do I extract leads through Jentic?

Search Jentic for 'extract leads from Sales Navigator', import the Evaboot operation, and store your token once. Your agent then starts extraction jobs and reads their results on demand. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Evaboot Public API

Name: Evaboot Public API
Brand: Evaboot
Availability: InStock

Official vendor OpenAPI document · agent-readyData EnrichmentContact Enrichmentbearer15 EndpointsREST

For Agents

Extract leads from Sales Navigator, find and validate professional emails, build search queries, and check quota through the Evaboot Public API. Jobs are started and then polled by id.

Use for: Extract leads from a Sales Navigator search, Find the email address for a specific lead, Validate a list of email addresses, Check the status of an extraction job

Not supported: Covers lead extraction, email finding, and email validation. Does not send outreach, manage CRM records, or run marketing campaigns.

The Evaboot Public API extracts leads from Sales Navigator and enriches them with verified contact details. You can start extraction jobs from a search URL or a single profile, find and validate professional email addresses, build search queries, and check your remaining quota. Jobs run asynchronously, so you start a job and read its result by id.

Jentic One on Github View OpenAPI Document

Connect the Evaboot Public API to your agent

Capabilities

Start building with Evaboot Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Evaboot Public API