PureChecker API
✓ Official Vendor SpecCommunicationsEmail DeliveryapiKey2 EndpointsREST
For Agents
Programmatically verify single email, verify bulk emails. Covers 2 operations with apiKey authentication.
Use for: I need to verify single email, I want to verify bulk emails, I need to access PureChecker API programmatically, I want to integrate PureChecker API into my workflow
Not supported: Does not handle payments, crm, or developer tools — use for communications only.
Email verification API for validating single and bulk email addresses. The API exposes 2 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the PureChecker API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PureChecker 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 PureChecker API.
Verify single email
Access PureChecker API resources via REST API
Access PureChecker API resources via REST API
Use Cases
Patterns agents use PureChecker API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'verify single email', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
2 endpoints — email verification api for validating single and bulk email addresses.
METHOD
PATH
DESCRIPTION
GET
/{email}
Verify single email
POST
/bulk-check
Verify bulk emails
GET
/{email}
Verify single email
POST
/bulk-check
Verify bulk emails
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
PureChecker API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'verify single email') and Jentic returns the matching PureChecker API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct PureChecker API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using PureChecker API through Jentic.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED