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

# Kitt

> Connect Kitt to verify email addresses in your workflows.

## How to set up Kitt

### Authentication

Kitt uses API key authentication:

1. Log in to your Kitt dashboard
2. Copy your API key
3. Paste the API key in Cargo when connecting

<Note>
  **Code slugs** — integration slug: `kitt` · action: `verifyEmail`. In a [workflow](/workflows/overview), declare the connector in `uses` and call `uses.<key>.verifyEmail(...)`.
</Note>

## Kitt actions

### Verify email

Verify an email address in real time and get its validity, SMTP status, and a reason when invalid.

**Required fields:**

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

**Credits:** 0.05 credits per request

**Use case:** Clean prospect lists before sequencing to protect sender reputation and reduce bounces.

## Best practices

* Verify emails right after enrichment, before they enter any outreach sequence
* Branch workflows on the returned validity and reason to route risky addresses separately
* Cache results to avoid re-verifying the same address repeatedly
* High-volume runs are handled for you: Cargo spreads requests within the connector's rate limit (100 per second)