Install Jentic One Beta

Connect the OrbiSearch Public API to your agent

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

Verify one email address and get a safe, risky, invalid, or unknown status with confidence and an explanation

Find a person's work email from a linkedin_url or from first_name, last_name, and domain

Enrich a company profile from its LinkedIn URL or website domain

Submit bulk verification, email-finder, or company-enrichment jobs and page through their results by job_id

GET STARTED

Start building with OrbiSearch Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

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

★ Agent-driven prospect email finding through Jentic

A sales-research agent with a list of LinkedIn profiles needs verified work emails, not guesses. Through Jentic the agent searches for 'find a work email from a LinkedIn URL', loads the OrbiSearch email-lookup operation with its input schema, and sends each linkedin_url with the X-API-Key header injected at call time. Each response returns the email with a status and confidence, plus employer_name, so the agent keeps only addresses marked safe.

POST /v1/email-lookup with linkedin_url 'https://www.linkedin.com/in/example' and keep the email only if status is 'safe'

Signup form email validation

Fake or mistyped addresses at signup create bounces later. GET /v1/verify checks one address in real time with a configurable timeout and returns is_disposable, is_role_account, and is_domain_catch_all flags alongside the status, so a form can reject disposable addresses and ask the user to correct invalid ones.

Call GET /v1/verify with email 'new.user@mailinator.com' and reject the signup if is_disposable is true or status is 'invalid'

List cleaning before a campaign

Before a newsletter send, a marketer cleans the list in one asynchronous job. POST /v1/bulk returns a job_id with total_emails and an estimated_cost, GET /v1/bulk/{job_id} reports progress, and GET /v1/bulk/{job_id}/results returns each address's verdict for removal of risky and invalid entries.

Submit the list with POST /v1/bulk, poll GET /v1/bulk/{job_id} until complete, then drop every address the results mark invalid

Pre-send spam check for outreach copy

Cold outreach that reads like spam lands in junk folders. POST /v1/content-spam-check takes the email content and an optional subject and returns a score, the threshold, a verdict, and the rules that fired, so a writer can edit flagged phrases before sending.

POST /v1/content-spam-check with the draft subject and content and list the rules that fired if the verdict is not passing

Key Endpoints

19 endpoints — the orbisearch public api verifies whether an email address will accept mail and finds work emails from a linkedin url or a name plus company domain.

METHOD

PATH

DESCRIPTION

GET

/v1/verify

Verify a single email

POST

/v1/email-lookup

Find an email by LinkedIn URL or name and domain

GET

/v1/company-enrichment

Enrich a company

POST

/v1/bulk

Submit bulk verification

GET

/v1/bulk/{job_id}/results

Get bulk verification results

POST

/v1/content-spam-check

Check email copy for spam triggers

GET

/v1/credits

Get credits

GET

/v1/verify

Verify a single email

POST

/v1/email-lookup

Find an email by LinkedIn URL or name and domain

GET

/v1/company-enrichment

Enrich a company

POST

/v1/bulk

Submit bulk verification

GET

/v1/bulk/{job_id}/results

Get bulk verification results

POST

/v1/content-spam-check

Check email copy for spam triggers

GET

/v1/credits

Get credits

Why Jentic?

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

Setup

Wiring OrbiSearch by hand means sending the X-API-Key header, respecting its per-key rate window and Retry-After backoff, and polling bulk job ids for verification, finding, and enrichment separately. Through Jentic you install once, import OrbiSearch from the API Directory, store the key once, and your agent calls it.

Permission scoping

Bulk job ids sit in the URL path (/v1/bulk/{job_id}/results), so a rule can pin your agent to reading one job's results. You choose the operations it may call, so credit-heavy ones like POST /v1/bulk or POST /v1/bulk-lookup are not included unless you add them.

Credential isolation

Your OrbiSearch 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 'verify an email address' or 'find a work email from LinkedIn', and Jentic returns the matching OrbiSearch operation with its input schema so the agent sends the right fields.

FAQs

Specific to using OrbiSearch Public API through Jentic.

What authentication does the OrbiSearch Public API use?

OrbiSearch authenticates with an API key sent in the X-API-Key header, as declared in its OpenAPI spec. Keys are issued from the OrbiSearch dashboard. Through Jentic the key is held by your own instance and attached at call time, so the agent never sees it.

Can OrbiSearch find an email from a LinkedIn profile?

Yes. POST /v1/email-lookup accepts a linkedin_url, or first_name, last_name, and domain, and returns the email with status, substatus, and confidence, plus full_name and employer_name. Substatus values include deliverable and no_address_found, among others.

What are the rate limits for the OrbiSearch Public API?

Per the OpenAPI spec, requests are limited per API key at 20 requests per second by default. Responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers, and a 429 response includes Retry-After with the suggested backoff in seconds.

Is there an OrbiSearch MCP server?

You don't need an MCP server to give your agent OrbiSearch. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the verify, lookup, and bulk operations on demand without loading another server's tool definitions into its context.

How do I verify an email through Jentic?

Search Jentic for 'verify an email address', load the GET /v1/verify operation, and execute it with the email parameter and an optional timeout. Read status and confidence from the response. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. For example, allow only GET /v1/verify and GET /v1/credits, and your agent can check single addresses and watch the balance while bulk jobs, which spend credits faster, stay out of reach. Every call it makes is logged.

OrbiSearch Public API

AI ReadinessAI-Aware (A-)72/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentContact EnrichmentapiKey19 EndpointsREST

For Agents

Verify email deliverability, find a person's work email from a LinkedIn URL or name and domain, enrich companies by domain, and spam-check email copy, singly or as bulk jobs.

Use for: Check whether jane.doe@acme.com is a deliverable address, Find the work email for a LinkedIn profile, I need to find Maria Lopez's email at globex.com, Enrich the company behind stripe.com

Not supported: Does not send email, host mailing lists, or track opens and clicks. Use for email verification, email finding, company enrichment, and spam-checking copy only.

The OrbiSearch Public API verifies whether an email address will accept mail and finds work emails from a LinkedIn URL or a name plus company domain. A single verification returns a status of safe, risky, invalid, or unknown with a substatus, confidence, MX record, and flags for catch-all domains, disposable addresses, role accounts, and free providers. Bulk jobs handle verification, email finding, and company enrichment asynchronously with status and paged results, and a spam check scores email copy against spam-trigger rules before it is sent.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

96%

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: A-Signals: 4

46%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

59%

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: CSignals: 4

60%

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.

64%

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

89%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the OrbiSearch Public API to your agent

Capabilities

Start building with OrbiSearch Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

OrbiSearch Public API

Jentic AI Readiness Score

OrbiSearch Public 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