Prime Verifier API
48
AI ReadinessFoundational (D+)48/100
Official vendor OpenAPI document · agent-readyData EnrichmentContact EnrichmentapiKey24 EndpointsREST
For Agents
Verify an email address or find someone's work email from first name, last name, and domain. Run single checks, batches of up to 30, or CSV bulk jobs and read back a verdict and risk score.
Use for: Check whether this email address is deliverable, Find the work email for Jane Doe at acme.com, I need to clean a CSV of leads before a campaign, Verify a batch of signup emails for disposable addresses
Not supported: Does not send email, host mailing lists, or run outreach campaigns. Use for verifying and finding email addresses only.
The Prime Verifier API verifies email addresses and finds a person's email from their name and company domain. Each verification checks syntax, DNS and MX records, disposable and role addresses, free providers, and real SMTP mailbox existence, then returns a headline result such as ok, invalid, catch_all, or disposable with a graded risk score. Single and batch calls cover up to 30 addresses at once, CSV bulk jobs handle large lists with live progress over Server-Sent Events, and webhooks report job events. Billing applies only to decisive results, so unknown and error verdicts are free.
Install Jentic One Beta
Connect the Prime Verifier API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Prime Verifier 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fprimeverifier.com%2Fprimeverifier" | sh2
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%2Fprimeverifier.com%2Fprimeverifier" | 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 Prime Verifier API.
Verify a single email address for syntax, MX records, disposable and role status, and SMTP mailbox existence
Verify up to 30 email addresses in one synchronous batch call
Find one person's email from firstName, lastName, and domain, with a Found or Not Found status and a Good, Risky, or Bad quality
Resolve up to 100 contacts to email addresses in one finder batch request
Upload a CSV for bulk verification or bulk finding and download the merged results file
Follow a bulk job's progress live over a Server-Sent Events stream
Register webhooks for job events and send a test delivery to confirm the URL is reachable
Use Cases
Patterns agents use Prime Verifier API for, with concrete tasks.
★ Agent-run lead email checks
An AI agent building a prospect list needs to know which addresses are real before outreach. Through Jentic the agent searches for 'verify an email address', calls the Prime Verifier single verify operation, and reads the result verdict and risk score for each address. For contacts without an address it calls the finder with firstName, lastName, and domain, and keeps only results whose quality is Good.
POST /v1/finder/single with firstName 'Jane', lastName 'Doe', and domain 'acme.com', then POST /v1/verify/single with the returned email and report the result and quality
Bulk list cleaning before a campaign
A marketing list exported as CSV can be cleaned without reformatting it. POST /v1/jobs accepts the original file with an emailColumn index and a dedupe flag, keeps every original column, and merges the verification columns back in at download time. While the job runs, GET /v1/jobs/{id}/download returns a partial file flagged with the X-Partial-Result header, so a pipeline can start working before the job completes.
Upload leads.csv to POST /v1/jobs with emailColumn 2 and dedupe true, follow GET /v1/jobs/{id}/stream until the done event, then download the results with GET /v1/jobs/{id}/download
Signup form quality gate
A signup flow can reject disposable and invalid addresses at the point of entry. GET /v1/verify/single takes the email as a query parameter and returns a verdict such as ok, invalid, catch_all, or disposable, so the backend can block throwaway accounts and flag catch_all domains for review. Unknown and error verdicts are not billed, which keeps the cost of transient failures at zero.
Call GET /v1/verify/single with email 'user@example.org' and reject the signup if result is 'invalid' or 'disposable'
Job notifications by webhook
Teams that run large verification or finder jobs can register a webhook URL with the event types they care about instead of polling. Each webhook gets an auto-generated signing secret, can be paused through the toggle or PATCH operations, and can be tested with a test delivery once active.
POST /v1/webhooks with url 'https://example.org/hooks/verify' and an events array, then POST /v1/webhooks/{id}/test to confirm delivery
Key Endpoints
24 endpoints — the prime verifier api verifies email addresses and finds a person's email from their name and company domain.
METHOD
PATH
DESCRIPTION
POST
/v1/verify/single
Verify a single email address
POST
/v1/verify/batch
Verify up to 30 addresses
POST
/v1/finder/single
Find one person's email
POST
/v1/finder/batch
Find emails for up to 100 contacts
POST
/v1/jobs
Start a CSV bulk verification job
GET
/v1/jobs/{id}/download
Download bulk job results
GET
/v1/credits/balance
Get credit balance
POST
/v1/webhooks
Create a webhook
POST
/v1/verify/single
Verify a single email address
POST
/v1/verify/batch
Verify up to 30 addresses
POST
/v1/finder/single
Find one person's email
POST
/v1/finder/batch
Find emails for up to 100 contacts
POST
/v1/jobs
Start a CSV bulk verification job
GET
/v1/jobs/{id}/download
Download bulk job results
GET
/v1/credits/balance
Get credit balance
POST
/v1/webhooks
Create a webhook
Jentic AI Readiness Score
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.
P
Prime Verifier API
- Foundational (D+)48/100
99
Foundational Compliance65
Developer Experience & Jentic Compatibility23
AI-Readiness & Agent Experience94
Agent Usability50
Security64
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
97%
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.
65
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
10%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
48%
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.
23
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
34%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
57%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
50
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).
64
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
64%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Prime Verifier by hand means sending the key in the X-API-KEY header, unwrapping the status, data, and error envelope, and handling multipart CSV uploads and Server-Sent Events for bulk jobs. Through Jentic you install once, import Prime Verifier from the API Directory, store the key once, and your agent calls it.
Permission scoping
Prime Verifier puts the job and webhook ids in the URL path (/v1/jobs/{id}, /v1/webhooks/{id}), so a rule can pin your agent to the verification operations it needs. You choose which operations it may call, so credit-heavy or destructive ones like CSV bulk jobs, job cancellation, or webhook deletion are not included unless you add them.
Credential isolation
Your Prime Verifier API key is stored once, encrypted, by your own Jentic One instance and injected into the X-API-KEY header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'verify an email address' or 'find someone's work email', and Jentic returns the matching Prime Verifier operation with its input schema so the agent sends firstName, lastName, and domain in the right shape.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Prime Verifier API through Jentic.
What authentication does the Prime Verifier API use?
Per its OpenAPI spec, the Prime Verifier API authenticates with an API key sent in the X-API-KEY header, declared globally for its operations. You create keys in the Prime Verifier dashboard under Profile, API Keys after registration and OTP verification. Through Jentic the key is held by your own instance and attached at call time.
Can I find someone's email address with the Prime Verifier API?
Yes. POST /v1/finder/single takes firstName, lastName, and domain, builds the candidate address formats itself, and probes them most-likely-first until it confirms a mailbox. The response gives a status of Found or Not Found and a quality of Good, Risky, or Bad. POST /v1/finder/batch handles up to 100 contacts, and POST /v1/finder/jobs takes a CSV for larger lists.
What are the rate limits for the Prime Verifier API?
The OpenAPI spec does not specify request rate limits. It does state size caps: up to 30 addresses per batch verify call, up to 100 contacts per finder batch, and a 50 MB file limit for bulk verification uploads. Check https://primeverifier.com for current account limits.
Is there a Prime Verifier MCP server?
You don't need an MCP server to give your agent Prime Verifier. Jentic connects it directly from the API Directory: import it, store your X-API-KEY once, and your agent calls the verify and finder operations on demand without loading another server's tool definitions into its context.
How do I verify an email through Jentic?
Search Jentic for 'verify an email address', load the POST /v1/verify/single operation, and execute it with the email in the request body. The agent reads the result and risk score from the data object in the response. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Prime Verifier API?
Yes. Write a rule that allows only POST /v1/verify/single, POST /v1/verify/batch, and GET /v1/credits/balance, so the agent can check addresses and watch its credit spend but cannot start bulk jobs or change webhooks. Every call it makes is logged for review.
Am I charged for unknown results?
No. The Prime Verifier spec states that billing applies only to decisive results, and unknown and error verdicts are free. GET /v1/credits/transactions lists Added, Used, and Adjusted credit movements if you want to reconcile spend.
GET STARTED