canonical: https://jentic.com/apis/reacher.email/reacher-email

# Reacher Email Reacher

What is Reacher? Reacher is a robust, open-source email verification API service available as both a SaaS and self-hosted solution. The API exposes 5 endpoints secured with apiKey authentication.

## For AI agents

Programmatically `/v1/check_email`, `/v1/bulk.` Covers 5 operations with apiKey authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- `/v1/check_email`
- `/v1/bulk`
- Retrieve bulk verification results
- `/v0/check_email`
- Access Reacher communications resources via REST API

## Use cases

### Communications Operations

Use the Reacher to perform communications operations programmatically. The API provides 5 endpoints covering core functionality including `/v1/check_email`, `/v1/bulk`, `/v1/bulk/{job_id}.`

Example prompt: Call POST `/v1/check_email` to `/v1/check_email`

### Automated Bulk Management

Automate bulk operations by combining multiple Reacher endpoints. Agents can `/v1/bulk` and then `/v1/bulk/{job_id}` in a single workflow.

Example prompt: Call POST `/v1/bulk` to `/v1/bulk`, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Reacher endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for '/v1/check_email', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/check_email` | `/v1/check_email` |
| POST | `/v1/bulk` | `/v1/bulk` |
| GET | `/v1/bulk/{job_id}` | `/v1/bulk/{job_id}` |
| GET | `/v1/bulk/{job_id}/results` | Retrieve bulk verification results |
| POST | `/v0/check_email` | `/v0/check_email` |

## Key resources

- **Bulk** — Operations for bulk
- **Check_Email** — Operations for check_email
- **V0** — Operations for v0

## Why Jentic

- **Setup:** Wiring Reacher by hand means passing its Authorization key header, choosing between the single-check and bulk endpoints, and polling bulk job status and results yourself. Through Jentic you install once, import Reacher from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Reacher takes the email address in the request body for its check operations, so you limit the agent to the operations it needs, such as check_email or submitting a bulk job. It only calls the operations you allow, so it verifies addresses without gaining any other capability.
- **Credential handling:** Your Reacher 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 'check if an email is deliverable' or 'submit a bulk verification job', and Jentic returns the matching Reacher operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Reacher use?

The Reacher uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I `/v1/check_email` with the Reacher?

Yes. Use the POST `/v1/check_email` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Reacher?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I `/v1/check_email` through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for '/v1/check_email'. Jentic returns the matching Reacher operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Reacher have?

The Reacher exposes 5 endpoints covering bulk, check_email, v0 operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Reacher operations and credentials the agent can use. You can allow only the operations it needs, such as checking a single email address with POST `/v1/check_email` or submitting a bulk job with POST `/v1/bulk`, while withholding everything else. Since Reacher takes the target email address in the request body, the agent can verify only the addresses you pass it and gains no other capability.