canonical: https://jentic.com/apis/blitz-api.ai/blitz-api

# Blitz API Reference

The Blitz API finds and enriches B2B people and company records for sales and go-to-market workflows. It searches for people and companies, finds employees at a target company, and builds a total-addressable-market list from job signals. It also enriches a contact with a work email or phone number, resolves a person from an email or phone, and enriches a company or maps a domain to a LinkedIn profile and back. The surface is built around lead discovery and contact enrichment keyed to companies, domains, and people rather than outreach sending or CRM storage.

## For AI agents

Enrich B2B leads: search people and companies, find employees, and enrich contacts with work email, phone, and company data keyed to domains and LinkedIn profiles.

## Scope

Does not handle email or message sending, CRM record storage, or payment. Use for B2B people, company, and contact enrichment only.

## Capabilities

- Search for people and companies matching a set of criteria
- Find employees at a target company for account-based prospecting
- Enrich a contact with a work email address or phone number
- Resolve a person record from an email address or phone number
- Enrich a company record and map a domain to its LinkedIn profile
- Build a total-addressable-market list from job-posting signals

## Use cases

### AI agent lead enrichment

An AI sales agent needs to turn a bare name or company into a contactable lead before it drafts outreach. Through Jentic the agent searches for the person, enriches them with a work email and phone, and pulls the company record behind their domain. Because enrichment and search are separate operations, the agent can enrich only the fields a workflow needs rather than pulling a full profile every time.

Example prompt: Search Jentic for 'find a work email for a prospect', call POST `/v2/search/people` to resolve the person, then POST `/v2/enrichment/email` to get their work email.

### Account-based prospecting

A go-to-market workflow needs the right contacts at a set of target companies. The company search and employee-finder operations return companies matching criteria and the people who work at them, so the workflow can build a contact list for each account. Pairing this with company enrichment attaches firmographic context to each account.

Example prompt: Call POST `/v2/search/companies` to find target accounts, then POST `/v2/search/employee-finder` for each to list contacts to reach out to.

### Domain and LinkedIn resolution

A data-cleanup workflow needs to normalise company records that arrive with only a domain or a LinkedIn URL. The domain-to-LinkedIn and LinkedIn-to-domain operations map between the two identifiers, and company enrichment fills in the rest of the record. This keeps a CRM's company data consistent regardless of which identifier a record started with.

Example prompt: Call POST `/v2/enrichment/domain-to-linkedin` to map a company domain to its LinkedIn profile, then POST `/v2/enrichment/company` to enrich the firmographic record.

### Total-addressable-market building

A market-sizing workflow needs a target list grounded in real hiring signals. The job-search and total-addressable-market operations surface companies hiring for relevant roles, so the workflow can assemble an account list tied to demand rather than static lists. This gives sales a prioritised set of accounts showing buying intent.

Example prompt: Call POST `/v2/jobs/search` to find companies hiring for a role, then POST `/v2/company/tam-by-jobs` to assemble the addressable-market list.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v2/search/people` | Search for people |
| POST | `/v2/search/companies` | Search for companies |
| POST | `/v2/search/employee-finder` | Find employees at a company |
| POST | `/v2/enrichment/email` | Enrich a contact with a work email |
| POST | `/v2/enrichment/phone` | Enrich a contact with a phone number |
| POST | `/v2/enrichment/company` | Enrich a company record |
| POST | `/v2/jobs/search` | Search job postings for buying signals |
| GET | `/v2/account/key-info` | Read API key account info |

## Why Jentic

- **Setup:** Wiring the Blitz API by hand means sending the x-api-key header on every request and tracking your credit balance yourself across search and enrichment calls. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Blitz API exposes search and enrichment operations, so a rule bounds which of them the agent may call: people search and email enrichment, without phone enrichment or the total-addressable-market build unless you add them. You choose the allowed set, so the agent only runs the operations you pick.
- **Credential handling:** Your Blitz 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 'find a work email for a prospect' or 'find employees at a company', and Jentic returns the matching Blitz operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Apollo** — Apollo offers B2B prospecting and contact enrichment as a broad alternative to Blitz
- **Clearbit** — Clearbit enriches company and contact records from a domain or email, similar to Blitz
- **People Data Labs** — People Data Labs provides person and company datasets for enrichment like Blitz
- **Hunter** — Hunter specialises in finding and verifying work email addresses, complementing Blitz enrichment

## FAQ

### Is there a Blitz API MCP server?

You don't need an MCP server to give your agent the Blitz API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent searches and enriches leads on demand without loading another server's tool definitions into its context.

### What authentication does the Blitz API use?

The Blitz API authenticates with an apiKey sent in the x-api-key header, per its OpenAPI spec. When you call it through Jentic, that key is stored encrypted by your own Jentic One instance and injected at execution time, so it never appears in the agent's prompt or logs.

### Can I find a work email for a prospect with the Blitz API?

Yes. After resolving the person with POST `/v2/search/people`, the POST `/v2/enrichment/email` endpoint returns a work email for the contact, and POST `/v2/enrichment/phone` does the same for a phone number, so an agent can build a contactable lead record.

### What are the rate limits for the Blitz API?

The OpenAPI spec does not specify rate limits for the Blitz API. Usage is metered against your plan's credit balance, which you can read with GET `/v2/account/key-info`, so check the provider's documentation at https://docs.blitz-api.ai for the limits and credit rules on your plan.

### How do I enrich a lead through Jentic?

Search Jentic for 'find a work email for a prospect', load the matching operation, call POST `/v2/search/people` to resolve the contact, then POST `/v2/enrichment/email` for their work email. 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 the Blitz API?

Yes. Because Jentic One is self-hosted, you decide which operations the agent may call: you might allow the search and email-enrichment operations while leaving out phone enrichment or the total-addressable-market build, and the calls the agent makes are logged.