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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpurechecker.com%2Fpurechecker" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpurechecker.com%2Fpurechecker" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

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

GET STARTED

Start building with PureChecker API

Explore with Jentic One

View OpenAPI Document

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?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

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

PureChecker API

Name: PureChecker API
Brand: PureChecker API
Availability: InStock

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail 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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

30%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PureChecker API to your agent

Capabilities

Use Cases

Start building with PureChecker API

Key Endpoints

Why Jentic?

Related APIs

FAQs

PureChecker API

Jentic AI Readiness Score

PureChecker API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness