canonical: https://jentic.com/apis/kickbox.com/kickbox

# Kickbox Email Verification API

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.

## For AI agents

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

## Scope

Does not send email, manage marketing lists, or score sender reputation - use for verifying email address deliverability and disposable status only.

## Capabilities

- 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
- Detect disposable email addresses to block throwaway signups
- Read the remaining verification credit balance on a Kickbox account

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Email Verification** — Verify single email addresses for deliverability, role, and disposable signals
- **Batch Verification** — Submit and track bulk verification jobs
- **Account** — Read the verification credit balance

## Why Jentic

- **Setup:** Wiring Kickbox by hand means passing its apikey query parameter, handling the api.kickbox.com host, and polling batch jobs yourself. Through Jentic you install once, import Kickbox from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Kickbox email to verify travels in the request, not as a URL path resource, so scope by operation: limit the agent to the operations it needs, such as verifying a single address or checking the disposable status, and leave batch submission or balance reads out unless you add them.
- **Credential handling:** Your Kickbox API key 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.
- **Discovery method:** Agents search Jentic by intent such as 'verify this email address' or 'check if an email is disposable', and Jentic returns the matching Kickbox operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **NeverBounce API** — NeverBounce offers similar single and bulk verification with comparable per-address pricing
- **Emailable API** — Emailable provides single and batch email verification with deliverability and disposable checks
- **Hunter API** — Hunter finds and verifies email addresses by domain and person name
- **Mailchimp Marketing API** — Mailchimp sends the campaigns that benefit from a Kickbox-cleaned list

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

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

### Can I limit what my agent is allowed to do with the Kickbox Email Verification API?

Yes. Because Jentic One runs self-hosted, you decide which Kickbox operations your agent can call, and your own rules are enforced at execution time. Since the email to verify travels in the request body rather than a URL path, you scope by operation: grant only the calls the agent needs, such as verifying a single address with GET /verify or checking disposable status with GET /disposable/{email}, while leaving batch submission via POST /verify-batch and balance reads via GET /balance out unless you add them. Your Kickbox API key stays with your own instance and is injected at call time, so the agent can only reach the operations you have approved.