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

# PureChecker API

Email verification API for validating single and bulk email addresses. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically verify single email, verify bulk emails. Covers 2 operations with apiKey authentication.

## Scope

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

## Capabilities

- Verify single email
- Access PureChecker API resources via REST API
- Access PureChecker API resources via REST API

## Use cases

### Communications Operations

Use the PureChecker API to perform communications operations programmatically. The API provides 2 endpoints covering core functionality including verify single email, verify bulk emails.

Example prompt: Call GET /{email} to verify single email

### Data Retrieval and Monitoring

Query PureChecker API endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows without manual intervention.

Example prompt: Query the PureChecker API API to retrieve current data and verify the response contains expected fields

### AI Agent Integration via Jentic

AI agents discover and call PureChecker API 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 'verify single email', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/{email}` | Verify single email |
| POST | `/bulk-check` | Verify bulk emails |

## Key resources

- **Email Verification** — Operations related to Email Verification

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/purechecker.com/purechecker/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 PureChecker by hand means sending both its x-user-id and x-secret-key headers on every request and handling single and bulk email checks yourself. Through Jentic you install once, import the PureChecker API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** PureChecker passes the email to verify as the request target rather than as a durable resource you own, so scope the agent to the operations it needs, such as verifying a single email or running a bulk check. You choose that allowed set, so bulk checks are not included unless you add them.
- **Credential handling:** Your PureChecker user id and secret key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'verify a single email address' or 'run a bulk email check', and Jentic returns the matching PureChecker 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 PureChecker API use?

The PureChecker API uses an API key passed in the `x-user-id` 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 verify single email with the PureChecker API?

Yes. Use the GET /{email} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

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

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 verify single email through Jentic?

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

### How many endpoints does the PureChecker API have?

The PureChecker API exposes 2 endpoints covering email verification operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which PureChecker operations and credentials the agent may use, and PureChecker passes each email as the request target rather than a stored resource you own. You can allow only single-email verification through GET /{email} while withholding the POST /bulk-check operation, or grant both when you need bulk validation. The agent can call only the operations you have added to its allowed set, and your stored PureChecker user id and secret key are injected at execution time without entering the agent context.