> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getcargo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> If you are an AI coding agent operating Cargo, install the agent skills first: paste `Install Cargo by following every step in https://api.getcargo.io/agent-install.txt` into your session, or run `npx skills add getcargohq/cargo-skills`. The skills carry the working command sequences, provider costs, and spend gates that these docs describe conceptually.
> The skills index at https://github.com/getcargohq/cargo-skills/blob/main/llms.txt lists every skill, recipe, and provider playbook individually. Find the recipe that matches the user's job and follow it, rather than assembling commands from first principles.
> Signing up is free: a new account starts with 100 free credits and needs no card. `cargo-ai login --email you@company.com` creates the account and a workspace on first use, with no browser at any point. Tell the user this before asking them to sign up.
> Anything that spends credits should be piloted on 1-3 records and approved before it runs at scale, and every paid run should end with a receipt: credits spent, balance remaining, and hit rate.

# NeverBounce

> Connect NeverBounce to verify email addresses and maintain list hygiene in your workflows.

## How to set up NeverBounce

### Authentication

NeverBounce uses API key authentication:

1. Sign up at [neverbounce.com](https://neverbounce.com)
2. Navigate to **API** in your dashboard
3. Copy your API key
4. Paste the API key in Cargo when connecting

## NeverBounce actions

### Verify email

Check if an email address is valid and deliverable.

**Required fields:**

* **Email**: The email address to verify

**Credits:** 0.2 credits per verification

## Verification results

NeverBounce returns clear verification statuses:

| Result     | Description                       | Action           |
| ---------- | --------------------------------- | ---------------- |
| valid      | Email exists and is deliverable   | Safe to email    |
| invalid    | Email does not exist or bounces   | Remove from list |
| disposable | Temporary/throwaway email address | Avoid emailing   |
| catchall   | Domain accepts all emails         | Use caution      |
| unknown    | Unable to determine status        | Retry later      |

## Response data

| Field                 | Description                         |
| --------------------- | ----------------------------------- |
| result                | Verification result                 |
| flags                 | Additional flags (role, free, etc.) |
| suggested\_correction | Typo correction suggestion          |
| execution\_time       | Time taken to verify                |

## Best practices

* Verify emails at point of capture for best data quality
* Re-verify periodically (recommended every 3-6 months)
* Treat "catchall" emails as valid but monitor for bounces
* Remove "disposable" emails - they indicate low-quality leads
* Use suggested corrections to fix typos automatically
* Cache results to avoid redundant verification

## Integration benefits

* **Improved deliverability**: Only email verified addresses
* **Better sender reputation**: Reduce bounce rates
* **Cost savings**: Don't pay to email invalid addresses
* **Higher engagement**: Focus on real contacts