canonical: https://jentic.com/apis/orbisearch.com/orbisearch

# OrbiSearch Public API

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.

## For AI 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.

## Scope

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.

## Capabilities

- 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
- Score email copy and subject for spam triggers and get a verdict against a threshold
- Check remaining credits or unlimited-plan usage before running a large job

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

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

## Key resources

- **Verification** — Single-address verification and bulk verification jobs with status and results
- **Email finder** — Find an email by LinkedIn URL or name and domain, singly or as bulk jobs, including unlimited-plan variants
- **Company enrichment** — Enrich a company by LinkedIn URL or domain, singly or as bulk jobs
- **Content spam check** — Score email copy and subject for spam triggers
- **Account** — Credits balance and unlimited-plan usage

## 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:** 72 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 76 / 100
  - AI-Readiness & Agent Experience: 56 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 89 / 100
- **View full report:** https://jentic.com/apis/orbisearch.com/orbisearch/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 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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Hunter** — Email finder and verifier by domain and name
- **ZeroBounce** — Email validation with bulk file processing
- **NeverBounce** — Real-time and bulk email verification
- **Apollo** — Prospect database for building lead lists

## FAQ

### 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.