Install Jentic One Beta

Connect the ContactLint API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ContactLint 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%2Fcontactlint.com%2Fcontactlint" | 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%2Fcontactlint.com%2Fcontactlint" | 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 ContactLint API.

Validate a single email address for deliverability and formatting

Validate up to 50 email addresses in one batch request

Verify that a phone number is valid and reachable

Check remaining credit balance and monthly usage for a key

Export every record stored against a key as JSON

GET STARTED

Start building with ContactLint API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ContactLint API for, with concrete tasks.

★ Agent-Driven Contact Validation

An AI agent that collects or processes contact details can call ContactLint through Jentic to confirm an email or phone number is valid before it acts, rather than sending to a dead address. The agent passes the address to the validation operation and reads back a deliverability result, without the developer wiring the bearer or x-api-key auth by hand. Jentic returns the matching operation and its input schema so the agent validates inline.

Validate the email address jane@example.com and only continue the signup if the result is deliverable

Email List Hygiene Before a Send

Marketing and outreach tools can clean a mailing list before a campaign to cut bounces and protect sender reputation. The batch validation operation accepts up to 50 addresses per call, bills per address, and counts as a single request toward the rate limit, so a tool can walk a large list in chunks and keep only deliverable addresses.

Submit a batch of up to 50 addresses to the batch validation operation and drop any that are not deliverable

Signup and Lead-Capture Validation

A signup or lead form can check the email and phone a visitor entered at the point of capture so bad contacts never enter the database. ContactLint validates the email for deliverability and the phone number for reachability in separate calls, letting the form reject typos and disposable addresses before submission.

Validate a submitted email and phone number and return a single pass or fail decision for the form

Key Endpoints

8 endpoints — the contactlint api checks whether an email address or phone number is valid and deliverable before you act on it.

METHOD

PATH

DESCRIPTION

POST

/v1/email/validate

Validate a single email address

POST

/v1/email/validate/batch

Validate up to 50 emails in one request

POST

/v1/phone/validate

Validate a phone number

GET

/v1/usage

Report usage and credit balance

GET

/v1/account/export

Export everything stored for a key as JSON

DELETE

/v1/account

Permanently delete a key and its data

POST

/v1/email/validate

Validate a single email address

POST

/v1/email/validate/batch

Validate up to 50 emails in one request

POST

/v1/phone/validate

Validate a phone number

GET

/v1/usage

Report usage and credit balance

GET

/v1/account/export

Export everything stored for a key as JSON

DELETE

/v1/account

Permanently delete a key and its data

Why Jentic?

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

Setup

Wiring ContactLint by hand means choosing between its bearer token and x-api-key header auth, batching email lists within the 50-address limit, and handling the 402 response when a key runs out of checks. Through Jentic you install once, import ContactLint from the API Directory, store the credential once, and your agent calls it.

Permission scoping

ContactLint carries the email or phone number in the request body, so rules bound which operations your agent may call, not which address. Limit it to the validation operations it needs, and leave account deletion and data export out unless you add them.

Credential isolation

Your ContactLint credential 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.

Intent-based discovery

Agents search Jentic by intent such as 'validate an email address' or 'check a phone number', and Jentic returns the matching ContactLint operation with its input schema so the agent calls the right endpoint directly.

FAQs

Specific to using ContactLint API through Jentic.

What authentication does the ContactLint API use?

The ContactLint API accepts either a bearer token or an API key in the x-api-key header, per its OpenAPI spec. Through Jentic the credential is stored once, encrypted, by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

Is there a ContactLint MCP server?

You don't need to run an MCP server to give your agent the ContactLint API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent can validate emails and phone numbers straight away.

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

Yes. ContactLint carries the email or phone number in the request body, so a rule bounds which operations your agent may call. Allow just the email and phone validation operations, so the agent can clean contact data but cannot delete your key or export its stored records, and every call it makes is logged.

Can I validate a batch of emails with the ContactLint API?

Yes. The batch validation operation accepts up to 50 email addresses in one request, bills per address, and counts as a single call toward your rate limit, so an agent can clean a list without making one request per address.

What are the rate limits for the ContactLint API?

The OpenAPI spec notes that a batch validation counts as a single request toward the rate limit but does not publish a numeric ceiling. Check the ContactLint documentation for the current limits on your plan.

How do I validate an email with the ContactLint API through Jentic?

Search Jentic for an intent like 'validate an email address' and it returns the ContactLint validation operation with its input schema, so your agent sends the address and reads back the deliverability result. To run it on your own infrastructure, install Jentic One from its GitHub repo.

ContactLint API

AI ReadinessFoundational (D-)41/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentContact Enrichmentbearer, apiKey8 EndpointsREST

For Agents

Validate email addresses one at a time or in batches of up to 50, and verify phone numbers, returning a deliverability result for each over a REST API. Authenticates with a bearer token or an API key in the x-api-key header.

Use for: Validate this email address before sending to it, Check whether a batch of emails are deliverable, Verify that a phone number is valid and reachable, Get my remaining validation credit balance

Not supported: Does not handle email sending, SMS delivery, or address geocoding. Use for email and phone validation only.

The ContactLint API checks whether an email address or phone number is valid and deliverable before you act on it. It validates a single email, runs batches of up to 50 addresses in one call, and verifies phone numbers, returning a structured result for each. Supporting operations report credit balance and usage, export everything stored against a key, and delete a key on request. Responses are JSON and authentication is a bearer token or an API key.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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

60%

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: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

38%

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: FSignals: 4

24%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

47%

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: CSignals: 1

55%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C+Signals: 1

58%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the ContactLint API to your agent

Capabilities

Start building with ContactLint API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

ContactLint API

Jentic AI Readiness Score

ContactLint 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