Kickbox Email Verification API

Name: Kickbox Email Verification API
Brand: Kickbox Email Verification API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey5 EndpointsREST

For Agents

Verify email addresses one at a time or in batches, detect disposable mailboxes, and check the verification credit balance on a Kickbox account.

Install Jentic One Beta

Connect the Kickbox Email Verification API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Kickbox Email Verification 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

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 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 Kickbox Email Verification API.

Verify a single email address and return deliverability, role-account, and free-mailbox flags

Submit a batch verification job covering thousands of addresses in one upload

Poll a batch job's status until results are ready for download

GET STARTED

Start building with Kickbox Email Verification API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Kickbox Email Verification API, keeping it validated and agent-ready. Kickbox verifies single addresses or whole lists, flags disposable mailboxes, and reports the credit balance left on an account. The single-address endpoint returns deliverability, role, free-mailbox, and disposable signals in one call, while the batch endpoint accepts large CSV-style lists and exposes a status endpoint to poll progress. Agents can use it to clean address lists before sending email or to validate an address inline at signup.

Use Cases

Patterns agents use Kickbox Email Verification API for, with concrete tasks.

★ Inline signup validation

Block invalid and disposable addresses at the moment a user signs up by calling GET /verify with the submitted email. The response includes a deliverability verdict and a disposable flag, so the form can show an inline error before account creation. Verification typically completes in well under a second per address.

Call GET /verify with the user's email and reject the signup if the result is undeliverable or disposable.

List cleaning before a campaign

Marketing operations teams can upload a list of addresses to POST /verify-batch before sending a campaign, then poll GET /verify-batch/{id} until the job completes. The cleaned list reduces bounce rates and protects the sending domain's reputation, and Kickbox bills only the credits consumed.

POST a list of 25,000 addresses to /verify-batch, poll /verify-batch/{id} every 30 seconds, and download the cleaned list when status is complete.

Disposable address screening for fraud prevention

Trust and safety teams can call GET /disposable/{email} to flag throwaway addresses that are correlated with fraudulent signups. The endpoint returns a single boolean signal that fits cleanly into a fraud-scoring pipeline.

Call GET /disposable/{email} and add 30 points to the fraud risk score when the disposable flag is true.

Agent integration via Jentic

An onboarding agent can use Jentic to discover the Kickbox verify operation, load the schema, and execute it with a vaulted API key, returning a structured deliverability verdict the rest of the workflow can branch on.

Search Jentic for 'verify an email address with Kickbox', load GET /verify, and execute it with the user's submitted address.

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for kickbox email verification api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/verify

Verify a single email address

POST

/verify-batch

Submit a batch verification job

GET

/verify-batch/{id}

Check batch job status

GET

/balance

Read remaining credit balance

GET

/disposable/{email}

Check whether an address is disposable

GET

/verify

Verify a single email address

POST

/verify-batch

Submit a batch verification job

GET

/verify-batch/{id}

Check batch job status

GET

/balance

Read remaining credit balance

GET

/disposable/{email}

Check whether an address is disposable

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Kickbox apikey query parameter is stored encrypted in the Jentic vault and injected per request, so agents call /verify and /verify-batch without ever reading the raw key.

Intent-based discovery

Agents search Jentic by intent, for example 'verify an email address', and the Kickbox GET /verify operation is returned with its parameter and response schema for direct execution.

Time to first call

Direct integration: about half a day to wire up auth, batch polling, and error handling. Through Jentic: under 30 minutes to search, load, and execute the relevant operations.

FAQs

Specific to using Kickbox Email Verification API through Jentic.

Why is there no official OpenAPI spec for Kickbox Email Verification API?

Kickbox does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Kickbox Email Verification API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Kickbox Email Verification API use?

Kickbox authenticates by appending an apikey query parameter to every request. Jentic stores that key in its vault and injects it at execution time, so the agent never holds the raw key in its prompt or logs.

Can I run a batch verification job with the Kickbox Email Verification API?

Yes. POST a list of addresses to /verify-batch to start a job, then poll GET /verify-batch/{id} to retrieve status and the result download URL when the job is complete.

What are the rate limits for the Kickbox Email Verification API?

The OpenAPI specification does not declare explicit rate limits. Kickbox bills per verification credit, so use GET /balance to track consumption and back off batch submissions if the balance drops below your safety threshold.

How do I verify an email with the Kickbox Email Verification API through Jentic?

Run pip install jentic, search Jentic for 'verify an email address with Kickbox', load the GET /verify operation, and execute it with the address. Jentic supplies the apikey query parameter from the vault and returns the deliverability verdict as a structured response.