> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revyops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Ark

> Connect an AI Ark API key so Find data workflow steps can look up a person's email, mobile phone or LinkedIn URL.

## What This Integration Does

AI Ark is a data provider. Connecting it lets a workflow's [Find data step](https://docs.revyops.com/user-guide/workflows.md#find-data-step) look a person up with AI Ark and add the email, mobile phone or LinkedIn URL it finds to that person in RevyOps. Choose **AI Ark** as the step's **Data provider**.

AI Ark is connected per workspace. Each workspace pastes its own AI Ark API key, and Find data steps for that workspace that use AI Ark spend credits from that AI Ark account.

> [!NOTE]
>
> AI Ark only appears on the Integrations page when Workflows access is switched on for your agency, because it is used by workflow steps only.
> A super admin can switch AI Ark off for an agency. Its tile then shows "Upgrade to Enterprise to Access" and Find data steps on AI Ark stop with "AI Ark is not available on your plan. Ask your agency admin."

## Setup

**1. Get an API key**

Sign in at **app.ai-ark.com**, open **Settings**, then **API Management**, and create a key.

**2. Open the integration**

Go to **Settings → Integrations**, find the **Data Providers** section and open **AI Ark**.

**3. Save the key**

Paste the key and click **Save key**. RevyOps saves it, then checks it against your AI Ark credit balance, which costs nothing, and shows **Key saved and checked.** If AI Ark refuses the key or can't be reached, the key is still saved and the panel says what went wrong.

The panel shows **API key connected** once a key is saved. Click **Remove**, then **Remove key** to confirm, to delete the key; Find data steps on AI Ark for that workspace then stop with "No AI Ark API key connected" until a key is saved again. The **Connect AI Ark** link on a Find data step opens this panel directly.

## How A Person Is Looked Up

AI Ark finds an email from a LinkedIn URL, so RevyOps starts from the person's LinkedIn URL. A person with none gets one found first from their email. A person with neither, but with a last name and a company domain, can still get a mobile phone, and that lookup returns their LinkedIn URL too, which then finds the email.

| What the step finds | Comes from | AI Ark credits |
| - | - | - |
| **Email** | The LinkedIn URL | 1 when an email is found, nothing otherwise |
| **Mobile phone** | The LinkedIn URL, or the name and company domain | 5 when a number is found, nothing otherwise |
| **LinkedIn URL** | The person's email, or the mobile lookup by name and company domain | 0.5 for every lookup from an email, **even when nothing is found** |

AI Ark can't find an email from a name and company alone. When a person has a name and company domain but no LinkedIn URL can be found for them, the email is skipped with the reason "AI Ark cannot look up an email by name and company". Use [MoltSets](https://docs.revyops.com/integrations/moltsets.md) on that step instead if your people often have no LinkedIn URL and no email.

A LinkedIn URL found on the way to what the step looks for is added to the person too, even if the step wasn't asked for it: it is already paid for, and it is only looked for when the person has none.

## Email Status

AI Ark checks every email it returns with BounceBan at the moment it finds it. The result becomes the new email's status from AI Ark: a confirmed mailbox is **Valid**, and a domain that accepts all mail is **Catchall**. An email AI Ark marks invalid is not added; the step's result lists it as skipped. An email at a free-mail domain, such as Gmail, is marked personal in the run log and the test results.

## When AI Ark Says No

| AI Ark answer | What happens |
| - | - |
| The key is refused | The step fails with "AI Ark refused the API key. Reconnect AI Ark under Integrations." |
| No credits left | The step fails with "AI Ark has no credits left on this account. Top up AI Ark, then rerun." Values found before it are still added |
| AI Ark rejects the input of a lookup | That lookup is skipped with the reason "AI Ark rejected the input"; the rest of the step still runs |
| Too many requests, or AI Ark is down | The step waits and tries again |

AI Ark allows 5 calls a minute per key, and one lookup can take up to three. RevyOps runs one AI Ark lookup every 45 seconds for each workspace, so 100 people take about 75 minutes.

Values found before a failure are still added, so a retry with **Only if missing** on doesn't pay for the same lookups twice. Run History keeps every attempt's lookups, so you can see what the first attempt bought.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.