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

# Datagma

> Connect Datagma to find emails and phone numbers in your workflows.

## How to set up Datagma

### Authentication

Datagma uses API ID authentication:

1. Sign up at [datagma.com](https://datagma.com)
2. Navigate to your API settings
3. Copy your API ID
4. Paste the API ID in Cargo when connecting

## Datagma actions

### Enrich person

Enrich a person from an identifier you already have, rather than from their name
and company.

**Required fields:**

* **LinkedIn URL or email**: LinkedIn profile URL or professional email address

**Optional fields:**

* **Country code**: Two-letter country code, to avoid matching a namesake

Returns the person's profile alongside their emails and phone numbers.

**Credits:** 8 credits per request

**Use case:** Enrich contacts captured from LinkedIn, or complete a record you
only have an email address for.

### Enrich person from personal email

Retrieve a person's profile from a personal email address — the one they signed
up with, rather than their work address.

**Required fields:**

* **Email**: Personal email address

Only supported for people outside of the EU.

**Credits:** 2 credits per request

**Use case:** Identify freemail signups so they can be routed and enriched like
any other lead.

### Find email

Find a person's email address using their name and company.

**Required fields:**

* **First name**: Person's first name
* **Last name**: Person's last name
* **Company name**: Company name

**Credits:** 1 credit per request

**Use case:** Discover professional email addresses for prospecting.

### Find phone

Get a person's phone number using their email or LinkedIn URL.

**Input fields (provide at least one):**

* **Email**: Person's email address
* **Personal LinkedIn URL**: LinkedIn profile URL

**Credits:** 8 credits per request

**Use case:** Get direct phone numbers for high-priority contacts.

### Find phone and email

Retrieve both phone number and email address in one request.

**Required fields:**

* **First name**: Person's first name
* **Last name**: Person's last name
* **Company name**: Company name

**Credits:** 8 credits per request

**Use case:** Get complete contact data in a single lookup.

## Credits summary

| Action                            | Credits |
| --------------------------------- | ------- |
| Enrich person                     | 8       |
| Enrich person from personal email | 2       |
| Find email                        | 1       |
| Find phone                        | 8       |
| Find phone and email              | 8       |

**Tip:** Use "Find phone and email" when you need both - it costs the same as finding phone alone but gives you both data points.

## Best practices

* Use combined action when you need both email and phone
* Provide company name for better matching accuracy
* Use LinkedIn URL for phone lookups when available
* Cache results to avoid redundant credit usage
* Prioritize phone lookups for high-value prospects due to credit cost