ContactOut for AI agents
ContactOut finds and verifies professional contact details, letting a recruiter or sales team turn a LinkedIn profile into a working email address. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in ContactOut.
Find an email from a LinkedIn profile
Find a person's work email address starting from their LinkedIn profile URL alone.
Verify an email address
Verify an email address is deliverable before adding it to an outreach campaign.
Check API usage stats
Check current API usage stats before running a large batch of lookups.
25 ContactOut actions, graded by risk.
Every ContactOut action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
15Look things up. Allowed by default.
- contactout.get_campaignGet Campaign
- contactout.search_peopleSearch People
- contactout.list_campaignsList Campaigns
- contactout.search_companiesSearch Companies
- contactout.get_api_usage_statsGet API Usage Stats
- contactout.list_decision_makersList Decision Makers
- contactout.get_linkedin_contact_infoGet LinkedIn Contact Info
- contactout.get_hashed_email_identifiersGet Hashed Email Identifiers
- contactout.find_linkedin_profile_by_emailFind LinkedIn Profile by Email
- contactout.get_bulk_email_verification_jobGet Bulk Email Verification Job
- contactout.get_linkedin_contact_info_batchGet LinkedIn Contact Info Batch
- contactout.get_linkedin_contact_info_batch_jobGet LinkedIn Contact Info Batch Job
- contactout.count_peopleCount People
- contactout.verify_emailVerify Email
- contactout.check_linkedin_contact_availabilityCheck LinkedIn Contact Availability
write
9Create and change things. Allow, or ask the user first.
- contactout.add_campaign_recipientsAdd Campaign Recipients
- contactout.create_bulk_email_verification_jobCreate Bulk Email Verification Job
- contactout.create_linkedin_contact_info_batch_jobCreate LinkedIn Contact Info Batch Job
- contactout.enrich_personEnrich Person
- contactout.stop_campaignStop Campaign
- contactout.start_campaignStart Campaign
- contactout.enrich_person_by_emailEnrich Person by Email
- contactout.enrich_linkedin_profileEnrich LinkedIn Profile
- contactout.enrich_companies_by_domainEnrich Companies by Domain
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- contactout.remove_campaign_recipientsRemove Campaign Recipients
ContactOut in three steps.
- 01Your users connect ContactOutThey add their ContactOut api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Bulk Email Verification Job” can wait for the user, and “remove Campaign Recipients” can be denied outright.
- 03Any agent can actYour agent calls ContactOut through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('contactout', { read: 'allow', write: 'ask', // create_bulk_email_verification_job destructive: 'deny', // remove_campaign_recipients }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How ContactOut connects.
Users add their ContactOut api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same ContactOut connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use ContactOut from any agent.
ContactOut and Arc0, answered.
Can I use ContactOut with Claude, ChatGPT or Cursor?
Yes. Connect ContactOut to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the ContactOut actions you allow.
How do users connect ContactOut?
Users add their ContactOut api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which ContactOut actions can my agent take?
25 in total: 15 read, 9 write and 1 destructive, such as “create Bulk Email Verification Job”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in ContactOut?
Yes. Actions like “remove Campaign Recipients” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call ContactOut too?
Yes. The same ContactOut connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug ContactOut into your agent.
Your users connect ContactOut once, under your brand. Your agent gets 25 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan