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

# ProxyCurl

> Enrich and search LinkedIn data with ProxyCurl

ProxyCurl is a LinkedIn data API that enables you to enrich profiles and search for people, companies, and jobs. The Cargo integration provides access to ProxyCurl's enrichment and search capabilities.

## Authentication

Connect to ProxyCurl using your API key.

### Connection details

| Field       | Description            |
| ----------- | ---------------------- |
| **API Key** | Your ProxyCurl API key |

***

## ProxyCurl actions

### Enrich

Retrieve detailed information about a person, company, role, or job.

**Object types**

| Type        | Description                          |
| ----------- | ------------------------------------ |
| **Role**    | Enrich by role and company name      |
| **Person**  | Enrich by name, company, title, etc. |
| **Company** | Enrich by domain, name, or location  |
| **Job**     | Enrich by LinkedIn job URL           |

**Person filters**

| Filter         | Description           |
| -------------- | --------------------- |
| Company domain | Domain of the company |
| First name     | Person's first name   |
| Last name      | Person's last name    |
| Location       | Person's location     |
| Title          | Job title             |

**Company filters**

| Filter           | Description             |
| ---------------- | ----------------------- |
| Company domain   | Domain of the company   |
| Company name     | Name of the company     |
| Company location | Location of the company |

### Search

Search for people, companies, or jobs matching specific criteria.

**Object types**

| Type        | Description             |
| ----------- | ----------------------- |
| **Person**  | Search for people       |
| **Company** | Search for companies    |
| **Job**     | Search for job postings |

***

## Credits

| Action | Cost                    |
| ------ | ----------------------- |
| Enrich | 1 credit per enrichment |
| Search | 1 credit per result     |

***

## Use cases

<AccordionGroup>
  <Accordion title="Lead enrichment" icon="user-plus">
    Enrich leads with LinkedIn profile data including experience and education.
  </Accordion>

  <Accordion title="Company research" icon="building">
    Get comprehensive company profiles from LinkedIn.
  </Accordion>

  <Accordion title="Role-based search" icon="briefcase">
    Find people by their current role and company.
  </Accordion>

  <Accordion title="Job monitoring" icon="magnifying-glass">
    Track job postings for hiring signals.
  </Accordion>
</AccordionGroup>

***

## Best practices

1. **Use multiple identifiers** - Provide domain + name for better match rates
2. **Rate limits** - ProxyCurl allows 300 requests per minute
3. **Cache results** - Results are cached to reduce credit usage on repeated lookups