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

# Forager

> Find personal emails and phone numbers with Forager

Forager is a contact data enrichment platform that provides personal emails and phone numbers from LinkedIn profiles.

## Authentication

Connect to Forager using your account ID and API key.

### Connection details

| Field          | Description             |
| -------------- | ----------------------- |
| **Account ID** | Your Forager account ID |
| **API key**    | Your Forager API key    |

***

## Forager actions

### Find personal email

Retrieve a person's personal email address.

**Configuration**

| Field            | Description          |
| ---------------- | -------------------- |
| **LinkedIn URL** | LinkedIn profile URL |

### Find work email

Retrieve a person's work email address.

**Configuration**

| Field            | Description          |
| ---------------- | -------------------- |
| **LinkedIn URL** | LinkedIn profile URL |

### Find phone

Retrieve a person's phone number.

**Configuration**

| Field            | Description          |
| ---------------- | -------------------- |
| **LinkedIn URL** | LinkedIn profile URL |

***

## Credits

| Action              | Cost      |
| ------------------- | --------- |
| Find personal email | 2 credits |
| Find work email     | 2 credits |
| Find phone          | 5 credits |

***

## Use cases

<AccordionGroup>
  <Accordion title="Multi-channel outreach" icon="envelope">
    Combine work and personal email for better response rates.
  </Accordion>

  <Accordion title="Phone outreach" icon="phone">
    Get direct phone numbers for high-priority prospects.
  </Accordion>

  <Accordion title="LinkedIn enrichment" icon="user-plus">
    Enrich LinkedIn profiles with contact information.
  </Accordion>
</AccordionGroup>

***

## Best practices

1. **Use LinkedIn URLs** - LinkedIn profile URLs provide the best match rates
2. **Prioritize work email** - Work emails typically have higher deliverability
3. **Cache results** - Results are cached to reduce credit usage