Browse published operations

Searches 70+ million enriched, verified and active company profiles using account filters — ideal for building target-account (ABM) lists. Includes Lookalike Search: pass up to 5 domains or LinkedIn company URLs in lookalikeDomains to find similar companies. 💳 Credit Usage: 0.1 credits per returned result (Lookalike Search included). E.g. size: 100 with 100 matches = 10 credits. 💡 Tip: Each result includes a company id (UUID). Use these IDs in the People Search filter contact.company to find people working at exactly these companies — more precise than matching by name. Company Identification: Name or Domain, Domain, LinkedIn, URL, Name, Social Media Link, Phone Number Company Details: Industry, Location, Products and Services, Social Media, Company Type, Founded Year, Operation Language, Geo Location Financial & Size: Employee Size, Annual Revenue, Funding Advanced Filters: Keywords, Employee by Department, Headcount Growth, Technologies, NAICS 🔗 Related Endpoints: • People Search — find the people at these companies (0.5/result) • Export People with Email — bulk-export those people with verified emails • Lists — exclude accounts you already work (free) 📥 Filter value lists: industries.csv (919) · technologies.csv (16,000+) · departments-and-functions.csv (592). All other allowed values are listed inline in the field

Identifies a person from an email address: if a person with that email exists in the AI Ark database, you get back their full profile (name, title, company, LinkedIn, and more) — similar to a People Search result, excluding valid email and mobile phone. Useful for enriching inbound leads, newsletter signups, form fills, and CRM records where you only have an email. A 404 means no profile with this email was found. The search parameter contains the email address to look up and is the only request field. 💳 Credit Usage: 0.5 credits per request. 🔗 Related Endpoints: • Export Single Person with Email — get a BounceBan-verified email for the identified person (1 credit) • Mobile Phone Finder — get their mobile number (5 credits/result) • Personality Analysis — personalize your outreach to this person (4 credits) 📥 Filter value lists: industries.csv (919) · technologies.csv (16,000+) · departments-and-functions.csv (592). All other allowed values are listed inline in the field descriptions below. Learn how to use this API to enrich leads inside Clay: Watch Video Rate limits: 5 requests per second by default. Customers using more than 450,000 credits per month can get custom rate limits — contact us at support@ai-ark.com or via the in-app chat. The hea

Run any People Search for a flat 1 credit per page and see who matches before spending per-result credits — the recommended first call of every list-building workflow. Validate your filters, check totalElements, inspect match quality, then send the exact same filter body to People Search or Export People with Email. 💳 Credit Usage: 1 credit per page — whether the page holds 25 or 100 results. A full page of 100 previews costs 1 credit; the same page on People Search costs 50 credits (0.5 × 100). Up to 100 results per page (default 25), max 10,000 results per search. Each preview result contains: • The person's real AI Ark id — accepted directly by Export Single Person with Email, no full search needed • First name, masked last name (e.g. Ba*e), title, headline, location, department/functions/seniority, position history with dates • The full company object: id, name, description, industry, headcount, revenue, HQ + office locations, keywords, NAICS/SIC • has* availability flags (hasmobile, hasskills, haseducations, …) — see what data exists before paying to enrich; has_mobile: true means a Mobile Phone Finder call (5 credits) has something to find Not included: unmasked last names, emails, phone numbers, and no trackId (email finding chains off People Search only). Body: identical to People Search — all account, contact and lists filters plus page and size. 🔗 <str

Finds a person's mobile phone number. Send linkedin (a full profile URL), or both name and domain. Returns status, error and data. data holds the person id, the LinkedIn URL and the phone numbers, or is null when no person or phone is found (HTTP 200 in both cases). Prefer this V2 over the older ai-ark-people-mobile-phone-finder-2.

Older V1 of ai-ark-people-mobile-phone-finder, same input and price. Prefer the V2 endpoint. Send linkedin (a full profile URL), or both name and domain. Returns id, linkedin and data (the phone numbers). V1 answers HTTP 404 when no person or phone is found, where V2 answers 200 with data: null.

Build reusable lists of people or companies, then reference them from People Search, Company Search and Export People with Email to exclude matches — the standard way to skip prospects you already contacted or accounts you want to avoid. 💳 Credit Usage: Free — lists never cost credits. ♻️ Reusable & rewritable: the same list id stays valid across many searches. Update it any time: mode: APPEND (default) adds values; mode: REPLACE rewrites the list with a completely fresh set of values. You can keep up to 50 lists per day. Each list can hold up to 10,000 items. Lists expire automatically after 24 hours — recreate them daily. How it works • No id → a new list is created (type is required). • Your existing id → the list is updated (APPEND merges, REPLACE overwrites). • Unknown id → a new list is created for you. Supported types: peopleid, companyid. 🔗 Related Endpoints: • People Search — exclude via lists.people_id • Company Search — exclude via lists.company_id • Export People with Email — suppress contacted people from bulk exports The header Content-Type: application/json must be included in the request.

Searches 400+ million enriched, verified and active person profiles using contact and/or account (company) filters — the starting point for building outbound lead lists. Each result contains the full person profile and their company data. Results do not include emails or phone numbers — enrich them with the endpoints listed under Related Endpoints below. 💳 Credit Usage: 0.5 credits per returned result (e.g. size: 25 with 25 matches = 12.5 credits). You only pay for results actually returned. ⚠️ Track ID: The response includes a trackId. Pass it to Find Emails by Track ID to get verified emails for this exact result set. The trackId can be used once and expires 6 hours after this response — submit it promptly. Contact Filters: Profile: Full Name, Social Media Link, LinkedIn, Location, Language Skills, Profile Badge, LinkedIn Follower & Connection Count Professional: Current & Past Company, Seniority, Department and Function, Experience (Current/Previous Title, Duration) Skills & Education: Skills, Certifications, Education (School, Degree, Field of Study, Date), Keywords, Social Media Account Filters: Company Identification: Name or Domain, Domain, LinkedIn, URL, Name, Social Media Link, Phone Number Company Details: Industry, Location, Products and Services, Social Media, Company Type, Founded Year, Operation Language, Geo Location Financial & Size: Employee Size, Annual Revenue, Funding Advanced Filters: Keywords, Employee by Department, Headcount Growth

V2 of Export Single Person with Email — Clay-compatible. Behaves exactly like /v1/people/export/single, except that when the person is not found or has no email it returns HTTP 200 with an envelope { status, error, data } and data: null (instead of the v1 404). Lookup uses id first, then url. You must provide either id or url; if both are empty the API returns 400 Bad Request. ✨ Recommended for Clay: this V2 endpoint gracefully returns HTTP 200 for both the found and not-found cases, which is what Clay expects when enriching leads. 💳 Credit Usage: 1 credit per successful call (0.5 Full Profile Enrichment + 0.5 real-time BounceBan-validated email), and 0 credits if we do not find a valid email. The charged amount is also returned in the X-Credit response header (e.g. -1.0), present only on the charged (email found) response. ✅ Email Verification: All emails (SMTP & CATCH_ALL) returned by the API are verified in real time by BounceBan — safe to send, no re-verification needed. Real errors (400 / 402 / 500) and gateway errors (401 / 429) are returned as-is with their real HTTP status — they are not wrapped. 🔗 Related Endpoints: • Export Single Person with Email (V1) — same pricing, 404 on not-found • Mobile Phone Finder (V2 – Clay Compatible) — add mobile numbers in the same Clay table • Export People with Email — bulk instead of row-by-row The header

Analyzes the skills, headline, and summary of a profile and returns a complete personality profile with ready-to-apply outreach guidance: DISC and OCEAN (Big Five) scores with an archetype label, plus selling and hiring blocks containing field-by-field email advice (subject, salutation, tone, length, bullet points, closing line), whatToSay / whatToAvoid talking points, and key decision traits (risk tolerance, decision speed, decision drivers). Pipe these into your email-generation prompts to personalize outreach at scale. 💳 Credit Usage: 4 credits per request. 🔗 Related Endpoints: • People Search — find the people (and their LinkedIn URLs) first (0.5/result) • Export Single Person with Email — their BounceBan-verified email (1 credit) • Reverse People Lookup — identify a person from an email/phone before analyzing them (0.5/request) The header Content-Type: application/json must be included in the request.

Triggers email finding for a previous People Search result set, using the trackId from the People Search API response. This is step 2 of the two-step list-building flow (search → find emails). 💳 Credit Usage: 1 credit per found valid email (0.5 for the people data + 0.5 for the real-time BounceBan-verified email) — and 0 credits for people where no valid email is found. Example: 25 people submitted, 18 valid emails found = 18 × 1 = 18 credits; the other 7 cost nothing. Unlike Export People with Email (0.5 per person regardless + 0.5 per found email), here you only pay for delivered emails. ✅ Email Verification: All emails (SMTP & CATCH_ALL) returned by the API are verified in real time by BounceBan — safe to send, no re-verification needed. ⚠️ Important: Each trackId can only be used once. After the first request, the track ID is consumed and subsequent requests with the same ID will fail. The trackId also expires 6 hours after the original People Search response. Provide a webhook URL to receive asynchronous notifications when email finding completes. When the job completes, we POST the result to your webhook URL. Auto-refund window: A submission that is charged but never delivered is auto-refunded after up to 10 hours. Rate limits (per token): If a token already has 500 requests in flight, a further submit is rejected with 400 too many pending requests — drain below the cap (or wait for completions), then retry. 10 jobs are processed at once. Limits are independent per service and per token. The response includes statistics</cod

Search and email finding in a single asynchronous call: exports up to 10,000 people matching the same account and contact filters as the People Search API, with real-time verified emails included. The recommended endpoint for bulk outbound list building. 💳 Credit Usage: 0.5 credits per exported person (charged for everyone, whether or not an email is found) + 0.5 credits per found valid email. Example: 1,000 people with 700 emails found = 1,000 × 0.5 + 700 × 0.5 = 850 credits. You only pay the email portion for emails verified in real time by BounceBan. Note: this differs from Find Emails by Track ID, which charges only for found emails. ✅ Email Verification: All emails (SMTP & CATCH_ALL) returned by the API are verified in real time by BounceBan — safe to send, no re-verification needed. Limit: size maximum is 10000. Exceeding this limit returns 400 Bad Request - pagination limit exceeded. Results are processed asynchronously; provide a webhook URL to receive a POST when the export completes, or poll Export People Statistics. Auto-refund window: A submission that is charged but never delivered is auto-refunded after up to 10 hours. Rate limits (per token): If a token already has 500 requests in flight, a further submit is rejected with 400 too many pending requests — drain below the cap (or wait for completions), then retry. 10 jobs are processed at once. Limits are independent per service and per token. The response returns a trackId and st