> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to NeverBounce

The NeverBounce connector lets your AI agent act in each user's NeverBounce account. Each user connects their own NeverBounce API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 10 tools.

**Authentication:** API Key
**Categories:** Marketing, Developer Tools
**Tools:** 10: 5 read, 4 write, 1 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=NEVERBOUNCE)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the NeverBounce connection

   In **AgentKit > Connections**, create a NeverBounce connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'neverbounce'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize NeverBounce:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'neverbounce_account_info_get',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "neverbounce"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize NeverBounce:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="neverbounce_account_info_get",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their NeverBounce credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'neverbounce_account_info_get',
  toolInput: {},
  connector: 'neverbounce',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="neverbounce_account_info_get",
    tool_input={},
    connection_name="neverbounce",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `neverbounce_account_info_get`

Get Account Info · Read-only

Get the NeverBounce account's remaining credits and bulk job counts.
Returns credits_info (paid and free credits used and remaining) and job_counts (completed, under_review, queued, processing).
Use neverbounce_account_info_get to check the credit balance before a verification or bulk job. Use neverbounce_jobs_search to list the jobs themselves.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `neverbounce_job_results_list`

List Bulk Job Results · Read-only

List the verified rows of a completed bulk job, one page at a time.
Returns total_results, total_pages, the query used, and results, each with the original data row and a verification object (result, flags, suggested_correction, address_info).
Use neverbounce_job_results_list to read per-address results. Use neverbounce_job_status_get for counts only.
Requires a complete job; check job_status with neverbounce_job_status_get first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`integer`, required): Numeric ID of the bulk verification job to read results for, as returned by neverbounce_job_create or neverbounce_jobs_search. Example: 289022.
- `items_per_page` (`integer`, optional): Rows per page, 1 to 1000. Defaults to 10. Example: 100.
- `page` (`integer`, optional): Page number to return, starting at 1. Defaults to 1. Example: 2.

Example input: `{"job_id":289022}`

### `neverbounce_job_status_get`

Get Bulk Job Status · Read-only

Get the status and counts of one bulk verification job.
Returns id, job_status (such as uploading, parsing, waiting, queued, running, complete, under_review or failed), filename, created_at, started_at, finished_at, total counts by result, bounce_estimate, percent_complete and failure_reason.
Use neverbounce_job_status_get to poll one known job. Use neverbounce_jobs_search to find jobs by filename or status. Use neverbounce_job_results_list to read verified rows once the job is complete.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`integer`, required): Numeric ID of the bulk verification job to check, as returned by neverbounce_job_create or neverbounce_jobs_search. Example: 289022.

Example input: `{"job_id":289022}`

### `neverbounce_jobs_search`

Search Bulk Jobs · Read-only

Search the account's bulk verification jobs, optionally filtered by job ID, exact filename or status.
Returns total_results, total_pages, the query used, and results, each with the same fields as neverbounce_job_status_get.
Use neverbounce_jobs_search to browse or find jobs. Use neverbounce_job_status_get when you already have the job_id.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filename` (`string`, optional): Return only jobs whose filename matches exactly. Example: signups-2026-11.csv.
- `items_per_page` (`integer`, optional): Jobs per page, 1 to 1000. Defaults to 10. Example: 25.
- `job_id` (`integer`, optional): Return only the job with this numeric ID. Example: 289022.
- `job_status` (`string`, optional): Return only jobs in this status. Example: complete. One of: `under_review`, `queued`, `failed`, `complete`, `running`, `parsing`, `waiting`, `uploading`.
- `page` (`integer`, optional): Page number to return, starting at 1. Defaults to 1. Example: 1.

Example input: `{}`

### `neverbounce_poe_confirm`

Confirm Widget Verification · Read-only

Confirm on the server that an email submitted through a form was the one the NeverBounce JavaScript widget verified (proof of entry).
Returns status and token_confirmed (true when the email, transaction and token match).
Use neverbounce_poe_confirm to guard against tampering with the client-side widget. Use neverbounce_email_verify to verify an address from the server instead.
Requires the transaction ID, confirmation token and result that the widget added to the submitted form.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `confirmation_token` (`string`, required): The confirmation token the widget added to the form, in the nb-confirmation-token field. Example: e3173fdbbdce6bad26522dae792911f2.
- `email` (`string`, required): The email address that was submitted with the form. Example: support@neverbounce.com.
- `result` (`string`, required): The verification result the widget reported for the address. Example: valid. One of: `valid`, `invalid`, `disposable`, `catchall`, `unknown`.
- `transaction_id` (`string`, required): The transaction ID the widget added to the form, in the nb-transaction-id field. Example: NBPOE-TXN-5942940c09669.

Example input: `{"confirmation_token":"<confirmation_token>","email":"<email>","result":"valid","transaction_id":"<transaction_id>"}`

### `neverbounce_email_verify`

Verify Email · Write

Verify one email address in real time and spend one NeverBounce verification credit.
Returns result (valid, invalid, disposable, catchall or unknown), flags such as has_dns_mx, role_account or free_email_host, suggested_correction and execution_time, plus address_info and credits_info when requested.
Use neverbounce_email_verify for one address at a time, such as at sign-up. Use neverbounce_job_create to verify a list. Verification can take several seconds for slow mail servers: keep timeout at 8 seconds or less so the call finishes inside the tool-call time limit.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, required): The email address to verify. Example: support@neverbounce.com.
- `address_info` (`integer`, optional): Set to 1 to add an address_info object that splits the address into normalized email, user, alias, host, domain, subdomain and TLD. Defaults to 0. Example: 1. One of: `0`, `1`.
- `credits_info` (`integer`, optional): Set to 1 to add a credits_info object with the paid and free credits used by this call and the credits remaining. Defaults to 0. Example: 1. One of: `0`, `1`.
- `leverage_historical_data` (`integer`, optional): Set to 0 to stop NeverBounce from using its historical verification data for this address and force a fresh check. NeverBounce uses historical data by default (1). Example: 0. One of: `0`, `1`.
- `timeout` (`integer`, optional): Longest time in seconds NeverBounce should try to verify before it gives up and returns unknown. Network time is extra. Use 8 or less to stay within the tool-call time limit. Example: 8.

Example input: `{"email":"<email>"}`

### `neverbounce_job_create`

Create Bulk Job · Write

Create a bulk verification job from a list of email records or from a file at a remote URL.
Returns job_id. Verification results are not in the response; the job runs in the background.
Use neverbounce_job_create to verify many addresses at once. Use neverbounce_email_verify for a single address. With auto_start set, credits are spent as soon as parsing ends; otherwise call neverbounce_job_parse and neverbounce_job_start, then poll neverbounce_job_status_get and read rows with neverbounce_job_results_list.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `allow_manual_review` (`boolean`, optional): Set true to let NeverBounce place the job in manual review. API jobs are not eligible by default. Example: false.
- `auto_parse` (`boolean`, optional): Set true to start indexing the list as soon as the job is created. When false or omitted, call neverbounce_job_parse next. Example: true.
- `auto_start` (`boolean`, optional): Set true to start verification as soon as parsing ends. This deducts credits and cannot be stopped. When false or omitted, call neverbounce_job_start next. Example: false.
- `callback_headers` (`object`, optional): Extra request headers to send with each callback to callback_url, as header-name to value pairs. Example: {"X-Callback-Token": "s3cr3t"}.
- `callback_url` (`string`, optional): URL that NeverBounce sends a POST with job_id and event to as the job changes state, such as job_parsed, job_completed or job_failed. Example: https://example.com/neverbounce/callback.
- `emails` (`array`, optional): The records to verify, when you supply the data directly. Each record is an object holding an email key plus any other columns you want kept with it, such as an ID or a name; object keys become column headers. A record can instead be an array of column values, which leaves out headers. Provide this or remote_url, not both. The whole request must stay under 25 MB. Example: [{"id": 12345, "email": "support@neverbounce.com", "name": "Fred McValid"}].
- `filename` (`string`, optional): Name shown for the job in the NeverBounce dashboard and used to find it with neverbounce_jobs_search. Example: signups-2026-11.csv.
- `leverage_historical_data` (`boolean`, optional): Set false to stop NeverBounce from using its historical verification data and force fresh checks for the whole list. NeverBounce uses historical data by default. Example: false.
- `remote_url` (`string`, optional): Direct link to a hosted file to verify instead of supplied records: a CSV file or one email per line. HTTP, HTTPS and FTP links work; put any username and password in the URL. Provide this or emails, not both. Example: https://example.com/full/path/to/file.csv.
- `run_sample` (`boolean`, optional): Set true to run a free sample of the list that returns an estimated bounce rate instead of verifying every address. Start the full run afterwards with neverbounce_job_start. Example: true.

Example input: `{}`

### `neverbounce_job_parse`

Parse Bulk Job · Write

Parse (index) a bulk job that was created without auto_parse.
Returns queue_id. A list can be parsed only once.
Use neverbounce_job_parse after neverbounce_job_create when auto_parse was off. Use neverbounce_job_start afterwards when auto_start is off.
Requires a job_id from neverbounce_job_create.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `job_id` (`integer`, required): Numeric ID of the bulk verification job to parse, as returned by neverbounce_job_create or neverbounce_jobs_search. Example: 289022.
- `auto_start` (`boolean`, optional): Set true to start verification, and spend credits, as soon as parsing ends. Defaults to false. Example: true.

Example input: `{"job_id":289022}`

### `neverbounce_job_start`

Start Bulk Job · Write

Start verifying a parsed bulk job. Credits are deducted and the run cannot be stopped or restarted.
Returns queue_id.
Use neverbounce_job_start when the job was created or parsed without auto_start. Set run_sample to get a free bounce-rate estimate first. Poll neverbounce_job_status_get for progress.
Requires a parsed job from neverbounce_job_create or neverbounce_job_parse.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `job_id` (`integer`, required): Numeric ID of the bulk verification job to start, as returned by neverbounce_job_create or neverbounce_jobs_search. Example: 289022.
- `allow_manual_review` (`boolean`, optional): Set true to let NeverBounce place the job in manual review. Defaults to false. Example: false.
- `run_sample` (`boolean`, optional): Set true to run a free sample that returns an estimated bounce rate instead of the full verification. Defaults to false. Example: true.

Example input: `{"job_id":289022}`

### `neverbounce_job_delete`

Delete Bulk Job · Destructive

Permanently delete a bulk verification job and its results.
Returns status success. The job and its results cannot be recovered; re-verifying the data spends credits again.
Use neverbounce_job_delete to remove a job you no longer need. Download or read results with neverbounce_job_results_list first.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `job_id` (`integer`, required): Numeric ID of the bulk verification job to delete, as returned by neverbounce_job_create or neverbounce_jobs_search. Example: 289022.

Example input: `{"job_id":289022}`

## Related

Other Marketing connectors ([all 190](/agentkit/connectors/?category=marketing)):

- [HubSpot](/agentkit/connectors/hubspot/): Scalekit connector, OAuth, 457 tools
- [Mailchimp](/agentkit/connectors/mailchimp/): Scalekit connector, OAuth, 73 tools
- [Twitter / X](/agentkit/connectors/twitteroauth/): Scalekit connector, OAuth, 92 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
