> Enrich.chat gives AI agents verified work emails and mobiles. To use it from an agent, read https://enrich.chat/agents.md . This is the Markdown version of https://enrich.chat/blog/apollo-api-key/

# How to get an Apollo API key in 2026: steps, key types, plan access, costs and errors

We read Apollo's developer docs and pricing page on October 16, 2026. Here is how to get a key, which kind to pick, how to test it, what a first call costs, and how to skip the key altogether.

By Enrich.chat Editorial. Updated October 16, 2026.

**Short answer:** To get an Apollo API key, open Settings, then Integrations, then API Keys in Apollo and click Create new key. Pick the endpoints it may call, or turn on Set as master key, then copy it, per [Apollo's key guide](https://docs.apollo.io/docs/create-api-key). You must be an admin or hold a permission profile that allows it. Send the key in an `x-api-key` header.

## Key takeaways

- Create the key at Settings, Integrations, API Keys. Only an admin, or a user whose permission profile allows it, can make one, per Apollo's developer FAQ.
- A scoped key works only for the endpoints you tick and returns a 403 for the rest. A master key reaches every endpoint, and a few endpoints need one.
- Send the key in the x-api-key header. Apollo says a key sent as a Bearer token returns 401 Invalid API key.
- A key acts as your workspace's longest-standing active admin, not as the person who made it. Treat it like a password.
- Apollo MCP and the Apollo CLI sign in with OAuth and need no key. Enrich.chat's API needs none either for its 10 free lookups a day.

## How do you get an Apollo API key?

You create an Apollo API key inside Apollo, under Settings, then Integrations, then API Keys. Click Create new key, choose what the key may call, and copy it. [Apollo's key guide](https://docs.apollo.io/docs/create-api-key) lists the steps, and it was last updated on August 31, 2026.

1. Open Apollo and click **Settings**, then **Integrations**, then **API Keys**.
2. Click **Create new key**.
3. Enter a name and a description. Select each endpoint the key may reach, or turn on **Set as master key** to select all of them.
4. Click **Create API key**.
5. Click **Copy** and paste the key into a secure place. Apollo shows the full key on that screen.

Name the key after its job, such as "crm-sync". Apollo's guide asks for names and descriptions with context, so the next admin knows what each key is for. You can regenerate a key or delete it for good from Apollo's developer dashboard. Its Usage tab shows credits used and the rate limits for each endpoint.

### Is an Apollo API key the same as a GraphQL or Reddit app key?

No. Search results for this keyword mix three products called Apollo, and this page covers Apollo.io, the sales platform. Apollo GraphOS keys belong to Apollo GraphQL, a separate company, and you create them in [GraphOS Studio](https://www.apollographql.com/docs/graphos/platform/access-management/api-keys) for routers, CI jobs and the CLI. The third product, a Reddit client app, is covered in our [Apollo API guide](https://enrich.chat/blog/apollo-api/). If your key came from studio.apollographql.com, it is not an Apollo.io key.

## Who can create an Apollo API key, and which plans include API access?

An admin, or a user with the right permission profile, can create a key. Every Apollo plan, Free included, has at least basic API access, but more advanced functionality needs certain plans. Both points come from [Apollo's developer FAQ](https://docs.apollo.io/docs/developer-faqs), updated September 29, 2026. The FAQ does not list which features count as advanced.

Apollo's own pages describe plan access in four slightly different ways. Here is each one as we read it on October 16, 2026:

- The [pricing page](https://www.apollo.io/pricing) comparison table ticks API Enrichment and All other APIs under Free, Basic, Professional and Organization. Its FAQ puts advanced or custom integrations on Custom plans.
- The [developer FAQ](https://docs.apollo.io/docs/developer-faqs) says all pricing plans include at least basic access.
- The [key guide](https://docs.apollo.io/docs/create-api-key) says access depends on your plan and points you to an upgrade or Apollo's sales team.
- A 403 with the code `API_INACCESSIBLE` means your plan lacks API access or the endpoint is closed to your credentials, per the [status codes page](https://docs.apollo.io/reference/status-codes).

Free accounts have one more rule. They must be registered with a work email address to use certain people and organization search, enrichment and record-retrieval endpoints, per [Build with Apollo](https://docs.apollo.io/docs/build-with-apollo). Paid accounts are not affected. Our [Apollo pricing guide](https://enrich.chat/blog/apollo-pricing/) covers each plan, and our [guide to Apollo.io](https://enrich.chat/blog/what-is-apollo-io/) covers the product.

The key is free to create, but its calls spend your plan's credits. This table shows how many email-plus-mobile lookups each plan's yearly credits cover. It uses [Apollo's pricing page](https://www.apollo.io/pricing), read on October 16, 2026, and the 9 credits [Apollo charges](https://docs.apollo.io/docs/api-pricing) for an email (1) plus a mobile (8).

| Apollo plan | Price per seat, billed annually | Credits per seat per year | Email-plus-mobile lookups (our math) |
| --- | --- | --- | --- |
| Free | $0 | 900 | 100 |
| Basic | $49 a month | 30,000 | 3,333 |
| Professional | $79 a month | 48,000 | 5,333 |
| Organization | $119 a month, 3 seats minimum | 72,000 | 8,000 |

Treat the last column as a ceiling. Apollo's pricing FAQ says unused credits expire at the end of each billing cycle, and monthly billing costs more per seat than annual billing.

## Should you create a scoped key or a master key?

Create a scoped key unless an endpoint needs a master key. A scoped key works only for the endpoints you select, and a call to any other endpoint returns a 403. A master key reaches every endpoint, and Apollo says to treat it like a password, per [its key guide](https://docs.apollo.io/docs/create-api-key).

### Which endpoint do you tick for each job?

Each endpoint's reference page has an "API key access" line. It names the scope to select, or says a master key also works. The [people enrichment reference](https://docs.apollo.io/reference/people-enrichment) lists `api/v1/people/match`. The [usage stats reference](https://docs.apollo.io/reference/view-api-usage-stats) lists `api/v1/usage_stats/api_usage_stats`. Its sample 403 names the endpoint path the key is missing, so a failed call tells you what to add.

### When do you need a master key?

- **Master-only endpoints.** A few, such as get a list of users, return a 403 without a master key, per Apollo's key guide.
- **Apollo MCP on a headless client.** Apollo MCP is not on the list of endpoints you can select, so a scoped key gets a 403 with the code `API_INACCESSIBLE`, per [Apollo's MCP docs](https://docs.apollo.io/docs/apollo-mcp).
- **Tools that ask for one.** [Polytomic's Apollo setup](https://docs.polytomic.com/docs/apollo) tells you to create a master key. [Nango's guide](https://nango.dev/docs/api-integrations/apollo/connect) shows both routes: tick the endpoints you need, or turn on the master key for all of them. Read the tool's own guide before you choose.

### Whose permissions does a key carry?

A key identifies a workspace, not a person. Every request made with a key acts as the workspace's longest-standing active admin, and that admin owns any records you create, per [Apollo's authentication page](https://docs.apollo.io/reference/authentication). Apollo's MCP docs add that a key made by a limited-permission user does not narrow what a headless client can reach. To see which user your key acts as, call `GET /users/api_profile` and read the returned `id`.

**Figure 1: One Apollo workspace, many keys, one acting user.** Three example keys feed into one Apollo workspace. A scoped key named crm-sync reaches contact endpoints. A scoped key named enrich-script reaches people match. A master key named mcp-server reaches every endpoint. Every request, whichever key sends it, acts as the workspace's longest-standing active admin, who owns the records created. Rate limits are shared by every key in the team and counted per endpoint. A note says a key made by a limited user still acts as the admin.

*Apollo keys differ in what they reach, but they share one acting user and one set of limits. The key names are examples. Sources: Apollo's [Create an API Key](https://docs.apollo.io/docs/create-api-key), [Authentication](https://docs.apollo.io/reference/authentication), [Rate Limits](https://docs.apollo.io/reference/rate-limits) and [Apollo MCP](https://docs.apollo.io/docs/apollo-mcp) pages, checked October 16, 2026.*

### How do you keep an Apollo API key safe?

Treat every key as a password. Apollo warns that anyone with access to a key may be able to take action in your Apollo account. These habits follow:

- Read the key from an environment variable or a secret manager, not from a file in your repository. Apollo's MCP docs give the same advice.
- Make one scoped key per integration, so you can delete one without breaking the others.
- Do not share a key with anyone you would not trust with admin access, because requests run as an admin.

## How do you test an Apollo API key, and why does it return a 401?

Send a GET request to `https://api.apollo.io/api/v1/auth/health` with the key in the `x-api-key` header. A working key returns `healthy` and `is_logged_in` as true, per [Apollo's test guide](https://docs.apollo.io/docs/test-api-key).

```
curl "https://api.apollo.io/api/v1/auth/health" \
  -H "x-api-key: $APOLLO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Cache-Control: no-cache"

# A working key returns:
# {"healthy": true, "is_logged_in": true}
```

If either value is false, Apollo says to remove stray spaces or line breaks after the key and retry. You can also paste the key into the Try It panel on an endpoint page in Apollo's docs. Or import Apollo's [OpenAPI file](https://docs.apollo.io/reference/openapi-specification) into Postman and send `GET /users/api_profile`, which Apollo says consumes no credits.

### Where does the key go in the request?

The key goes in the `x-api-key` header. Apollo's OpenAPI guide warns that a key entered as a Bearer token returns `401 Invalid API key`, because Bearer tokens are for OAuth partners. Some third-party guides still show a Bearer header for Apollo, such as [UpLead's May 2024 guide](https://www.uplead.com/apollo-io-api/), so check which format a guide uses before you copy it.

**Figure 2: Where the Apollo API key goes in a request.** Two requests. The first, which works, is a POST to api.apollo.io/api/v1/people/match with Content-Type and Cache-Control headers and the key in an x-api-key header. The second, which fails, sends the key as Authorization: Bearer and gets a 401 Invalid API key. A note says Bearer tokens are for OAuth apps only, and to read the key from an environment variable, not from your code.

*The key belongs in the x-api-key header. A Bearer header returns 401 for an API key. Sources: Apollo's [OpenAPI Specification](https://docs.apollo.io/reference/openapi-specification) and [Authentication](https://docs.apollo.io/reference/authentication) pages, checked October 16, 2026.*

### What do Apollo's key errors mean?

Apollo uses standard HTTP codes, listed on its [status codes page](https://docs.apollo.io/reference/status-codes). These four are the ones you meet while setting up a key:

| Code | What it means at Apollo | What to try |
| --- | --- | --- |
| `401` | The key is missing or invalid, or the account is no longer active | Send the key in x-api-key, remove trailing spaces, confirm the key still exists |
| `403` | The plan lacks API access, the scoped key lacks this endpoint, or the endpoint is not open to your credentials | Add the endpoint to the key, use a master key where one is required, or check the plan |
| `422` | Apollo got the request but could not process it, usually a missing or invalid parameter | Read the response body for the field at fault |
| `429` | You went over a rate limit | Wait the number of seconds in the retry-after header |

Newer errors carry an `error_details` object with a stable code. Branch your code on that code, not on the message. On February 16, 2027, Apollo removes the older top-level error fields, so move any logic that reads them. Both points are on Apollo's status codes page.

## What does your first call with the key cost, and what are the limits?

People search costs 0 credits, and people enrichment costs 1 to 9 credits per person. Enrichment charges 1 credit for the profile or email and 8 more if a mobile comes back, and nothing when it finds no credit-consuming data. These figures come from [Apollo's API pricing page](https://docs.apollo.io/docs/api-pricing), updated October 7, 2026.

People enrichment is the usual first call. This request matches one person by name and company domain and does not ask for a phone, so no webhook is needed:

```
Q="first_name=Jane&last_name=Doe&domain=example.com"

curl -X POST "https://api.apollo.io/api/v1/people/match?$Q" \
  -H "x-api-key: $APOLLO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Cache-Control: no-cache"
```

A match returns a `person` object with fields such as `name`, `title`, `email`, `email_status` and `organization`, per [Apollo's enrichment tutorial](https://docs.apollo.io/docs/enrich-people-data). An illustrative response is below, trimmed to those fields. Jane Doe and example.com are fictional.

```
{
  "person": {
    "name": "Jane Doe",
    "title": "VP Operations",
    "email": "jane.doe@example.com",
    "email_status": "verified",
    "organization": {"name": "Example Logistics", "primary_domain": "example.com"}
  }
}
```

Apollo warns that a name without a domain or email can return a 200 with nothing enriched, so check `match_confidence`. Mobile numbers need `reveal_phone_number=true` and a webhook, which our [Apollo API guide](https://enrich.chat/blog/apollo-api/) explains with code.

### How many credits does a batch use?

Say you enrich 100 people and want an email and a mobile for each. That is 100 x 1 plus 100 x 8, or 900 credits. It equals a Free seat's whole year of credits and 3% of a Basic seat's 30,000. The Basic share costs about $17.64 at Basic's annual rate of $588 for 30,000 credits, which is $0.0196 a credit. That is our math and assumes you use every credit.

### What are the rate limits?

Limits are per team and per endpoint, not per key, so a second key does not raise them. On paid plans, enrichment allows 1,000 requests a minute with no hourly or daily cap, and search allows 200 a minute and 50,000 a day. The Free plan allows 50 a minute and 600 a day. All of this is on [Apollo's rate limits page](https://docs.apollo.io/reference/rate-limits), updated August 21, 2026. A 429 includes a `retry-after` header. `POST /usage_stats/api_usage_stats`, which Apollo lists at 0 credits, shows your team's real limits.

## Do you need an API key for Apollo MCP or the Apollo CLI?

No. Apollo MCP and the Apollo CLI sign in with OAuth 2.0, so neither needs an API key, per [Build with Apollo](https://docs.apollo.io/docs/build-with-apollo) and the [Apollo CLI docs](https://docs.apollo.io/docs/apollo-cli-overview). The exception is a headless MCP client, such as a server or CI job with no browser. It sends a master key in the `X-Api-Key` header, per [Apollo's MCP docs](https://docs.apollo.io/docs/apollo-mcp).

Apollo's overview table marks MCP as OAuth only, but the newer MCP page describes the headless key route, so we follow the MCP page. Apollo MCP has its own rate limits and returns no rate limit headers. Our [Apollo MCP guide](https://enrich.chat/blog/apollo-mcp-alternative/) covers setup in Claude and what each call costs.

**Figure 3: Which credential each way of connecting needs.** A two-column map from what you are connecting to what you need. A script, app or automation tool that calls Apollo needs a scoped API key sent in the x-api-key header. An AI client or the Apollo CLI on a machine with a browser signs in with OAuth and needs no API key. Apollo MCP from a server or CI job with no browser needs a master API key sent in the X-Api-Key header. An app used by other Apollo customers is an OAuth 2.0 app that acts as the user who approves it. Contact data in an app or agent with no Apollo seat can use the Enrich.chat free tier, with no key and no signup.

*What each way of connecting needs. Sources: Apollo's [Build with Apollo](https://docs.apollo.io/docs/build-with-apollo), [Apollo MCP](https://docs.apollo.io/docs/apollo-mcp) and [Authentication](https://docs.apollo.io/reference/authentication) pages, and Enrich.chat's [agents.md](https://enrich.chat/agents.md), checked October 16, 2026.*

## What if you do not want to manage a key? How does Enrich.chat handle it?

Enrich.chat's API needs no key and no signup for its 10 free lookups a day per IP address. A key is optional: it comes with a paid plan and lifts the free cap. If you only need contact data in a script, an app or an AI agent, you can skip admin rights, endpoint scopes and header setup and send one GET request.

Here is a job you might do with an Apollo key, done with [Enrich.chat's person enrichment API](https://enrich.chat/api/person-enrichment/). `GET /v1/person` takes a LinkedIn URL, a work email, or a name plus a company website. The `fields` parameter picks email, mobile or profile. Enrich.chat never logs in to LinkedIn, so the URL is only a lookup key.

```
# Illustrative request. Jane Doe is fictional.
curl -G "https://enrich.chat/v1/person" \
  --data-urlencode "linkedin_url=linkedin.com/in/jane-doe-example" \
  --data-urlencode "fields=email,mobile"
```

An illustrative response looks like this:

```
{
  "found": true,
  "name": "Jane Doe",
  "title": "VP Operations",
  "company": {"name": "Example Logistics"},
  "linkedin_url": "https://www.linkedin.com/in/jane-doe-example",
  "work_email": {"value": "jane.doe@example.com", "status": "verified"},
  "mobile": {"value": "+1 415 555 0142", "line": "mobile"},
  "credits_used": 260,
  "free_lookups_remaining": 9
}
```

Each work email comes back with a status: `verified`, `catch_all` or `unknown`. A catch-all domain accepts every address, so the mailbox cannot be confirmed. Each mobile comes back with a line type, `mobile` or `unknown`. These are labels, not delivery guarantees, so treat every contact as a strong lead. If nothing matches, you get `"found": false` and nothing is used.

The `credits_used` value here is 260: 10 for the work email and 250 for the mobile. The `free_lookups_remaining` value is 9 because one of the day's 10 was used. Agents keep to about one request a second.

### How do you get a key when you need one?

When the free lookups run out, the API returns a 402 with the code `free_limit_reached` and an `upgrade_url`. To continue, log in on the [account page](https://enrich.chat/account/) with your email and a one-time code, pick a plan and pay at checkout. Your key appears there and starts with `pp_`. Send it as `Authorization: Bearer pp_...` or as `?key=pp_...`. Credits renew with each monthly payment, and unused credits do not roll over. The [pricing page](https://enrich.chat/pricing/) lists every plan.

### What does the same job cost on each side?

Take 100 people, with a work email and a mobile for each. On Apollo that is 900 credits, as worked out above. On Enrich.chat it is 26,000 credits, which fits the Growth plan at $29 a month, with unlimited seats and no annual contract. Pro-rated at that plan's own rate, the 100 lookups use $7.54 of credits. Apollo's 900 credits come to about $17.64 pro-rated at Basic's annual rate.

The units differ, so compare bills, not credit counts. Apollo bills a seat by the year. Enrich.chat bills a plan by the month. Pro-rated numbers assume you use every credit and are not what you pay. On both sides, a lookup that finds nothing uses 0 credits.

To skip the HTTP call, add the MCP server at enrich.chat/mcp. It needs no key, and the [install page](https://enrich.chat/install/) has the steps for each app. You can also run the same lookup in a browser with the free [email finder](https://enrich.chat/tools/email-finder/). Or paste this prompt into an agent:

```text
Use www.enrich.chat to find the work email and mobile for each LinkedIn URL I paste. Start on the free tier without a key and stop if you reach the limit. Show each email's status and each mobile's line type, mark misses as not found, and report credits_used and free_lookups_remaining after each lookup.
```

### What are Enrich.chat's limits?

- **It is not a CRM.** Enrich.chat returns data and keeps your saved lists. It does not enroll people in sequences or send email, so it cannot replace Apollo's contact and sequence endpoints.
- **The inputs are narrow.** `/v1/person` takes a LinkedIn URL, a work email, or a name plus a company website. A company name alone is not supported, and personal mailboxes such as Gmail are not looked up.
- **Searches and jobs have caps.** A search returns up to 25 people per call and at most 1,000 results. A [background job](https://enrich.chat/features/background-jobs/) holds at most 5,000 rows, and its results are kept 30 days.
- **There is no Chrome extension, and SDKs are planned, not available.** You call the API over plain HTTPS.

## When is an Apollo API key the right choice?

An Apollo API key is the right choice when Apollo is already where your team works. The key lets your code read and write the same records your reps see, and many of those calls cost nothing.

- **You work in Apollo every day.** Endpoints that create, update, list or manage records use 0 credits, per [Apollo's API pricing page](https://docs.apollo.io/docs/api-pricing). Only saved Apollo contacts can join Apollo sequences, as our [Apollo API guide](https://enrich.chat/blog/apollo-api/) explains.
- **You want company search, job postings or news from the same vendor.** Apollo prices each at 1 credit per page, on the same credits.
- **Your seats are already paid for.** If a seat has spare credits each cycle, API calls use money you have spent.
- **You are a partner building for shared customers.** Use OAuth 2.0, not a shared key, so each request acts as the user who approved it.

An Apollo key is a weaker fit when you build a product that shows Apollo data to your own customers, because Apollo says that needs a custom agreement. For contact data in an app or an AI agent without an Apollo seat, see how [Enrich.chat works as an alternative to Apollo MCP](https://enrich.chat/blog/apollo-mcp-alternative/). Whichever route you pick, you are responsible for TCPA rules on calls and texts and for CAN-SPAM and GDPR on email. This is not legal advice. Anyone can ask to be removed from Enrich.chat at [enrich.chat/opt-out/](https://enrich.chat/opt-out/), and the [terms](https://enrich.chat/terms/) cover account use.

## Frequently asked questions

### How do I get an Apollo API key?

In Apollo, click Settings, then Integrations, then API Keys, then Create new key. Enter a name and description, select the endpoints the key may call or turn on Set as master key, click Create API key, and copy the key somewhere secure. You must be an admin or have a permission profile that allows it, per [Apollo's developer FAQ](https://docs.apollo.io/docs/developer-faqs). Test the key with a GET request to /auth/health.

### Is the Apollo API key free?

Creating a key costs nothing, and every Apollo plan, Free included, has at least basic API access, per [Apollo's developer FAQ](https://docs.apollo.io/docs/developer-faqs). Calls still spend credits. People search uses none, and people enrichment uses 1 credit for an email plus 8 for a mobile. The Free plan grants 900 credits a seat a year, per [Apollo's pricing page](https://www.apollo.io/pricing), checked October 16, 2026.

### Why does Apollo say Invalid API key?

Apollo returns a 401 when the key is missing or invalid, or the account is no longer active. Check the header first: send the key as x-api-key, because Apollo's [OpenAPI guide](https://docs.apollo.io/reference/openapi-specification) says a key sent as a Bearer token returns 401 Invalid API key. Then remove any spaces or line breaks after the key, and confirm the key was not deleted.

### What is the difference between an Apollo master key and a scoped key?

A scoped key, the default, works only for the endpoints you select, and any other endpoint returns a 403. A master key reaches every endpoint, and a few endpoints, such as get a list of users, only work with one. Apollo tells you to create a master key only when an endpoint requires it and to treat it like a password, per [its key guide](https://docs.apollo.io/docs/create-api-key).

### Do I need an API key to use Apollo MCP?

No for most clients. Apollo MCP at mcp.apollo.io/mcp signs in with OAuth 2.0, per [Apollo's MCP docs](https://docs.apollo.io/docs/apollo-mcp). A server or CI job with no browser can send a master key in an X-Api-Key header instead. Enrich.chat's MCP server at enrich.chat/mcp also needs no key, and the [install page](https://enrich.chat/install/) has the steps.

### Can I get contact data without an Apollo API key?

Yes. Enrich.chat's [person API](https://enrich.chat/api/person-enrichment/) needs no key and no signup for 10 free lookups a day. Send a LinkedIn URL, a work email, or a name plus a company website to /v1/person. A key is optional and comes with a paid plan. Enrich.chat returns data and saved lists only, so it has no CRM records or sequences like Apollo's.

## Sources

1. [Create an API Key](https://docs.apollo.io/docs/create-api-key)
2. [Test an API Key](https://docs.apollo.io/docs/test-api-key)
3. [Authentication](https://docs.apollo.io/reference/authentication)
4. [Developer FAQs](https://docs.apollo.io/docs/developer-faqs)
5. [Build with Apollo](https://docs.apollo.io/docs/build-with-apollo)
6. [API Pricing and Credits](https://docs.apollo.io/docs/api-pricing)
7. [Rate Limits](https://docs.apollo.io/reference/rate-limits)
8. [Status Codes and Errors](https://docs.apollo.io/reference/status-codes)
9. [OpenAPI Specification](https://docs.apollo.io/reference/openapi-specification)
10. [People Enrichment](https://docs.apollo.io/reference/people-enrichment)
11. [View API Usage Stats and Rate Limits](https://docs.apollo.io/reference/view-api-usage-stats)
12. [Apollo MCP](https://docs.apollo.io/docs/apollo-mcp)
13. [Apollo CLI](https://docs.apollo.io/docs/apollo-cli-overview)
14. [Enrich People Data](https://docs.apollo.io/docs/enrich-people-data)
15. [Apollo.io pricing plans](https://www.apollo.io/pricing)
16. [Apollo.io: Polytomic setup guide](https://docs.polytomic.com/docs/apollo)
17. [Apollo API connection guide](https://nango.dev/docs/api-integrations/apollo/connect)
18. [Apollo API: Making The Most of Your Data](https://www.uplead.com/apollo-io-api/)
19. [API keys (GraphOS)](https://www.apollographql.com/docs/graphos/platform/access-management/api-keys)

## Try this prompt

Look up contacts without an API key

```text
Use www.enrich.chat to find the work email and mobile for each LinkedIn URL I paste. Start on the free tier without a key and stop if you reach the limit. Show each email's status and each mobile's line type, mark misses as not found, and report credits_used and free_lookups_remaining after each lookup.
```

## Related

- [Apollo API: endpoints, credit costs, rate limits and code](https://enrich.chat/blog/apollo-api/)
- [Apollo MCP: setup, costs and a no-sign-in alternative](https://enrich.chat/blog/apollo-mcp-alternative/)
- [Person enrichment API](https://enrich.chat/api/person-enrichment/)