Aeroleads for AI agents
AeroLeads is a B2B lead generation tool that finds business emails and phone numbers for prospects from their LinkedIn profiles. Sales teams use it to build outreach lists. 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 Aeroleads.
Look up a LinkedIn profile
Pull a prospect's business email and phone number from their LinkedIn profile URL before outreach.
Verify a prospect's contact info
Confirm the email and phone number found for a LinkedIn profile before adding it to a lead list.
Enrich a lead record
Add the contact details pulled from LinkedIn onto an existing lead record in the CRM.
1 Aeroleads actions, graded by risk.
Every Aeroleads action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- aeroleads.get_details_from_linkedin_urlGet Details From LinkedIn URL
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Aeroleads in three steps.
- 01Your users connect AeroleadsThey add their Aeroleads api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Aeroleads through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('aeroleads', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Aeroleads connects.
Users add their Aeroleads 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 Aeroleads 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 Aeroleads from any agent.
Aeroleads and Arc0, answered.
Can I use Aeroleads with Claude, ChatGPT or Cursor?
Yes. Connect Aeroleads 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 Aeroleads actions you allow.
How do users connect Aeroleads?
Users add their Aeroleads 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 Aeroleads actions can my agent take?
1 in total: 1 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Aeroleads?
Yes. Allow read actions and deny writes in the Aeroleads policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Aeroleads too?
Yes. The same Aeroleads connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Aeroleads into your agent.
Your users connect Aeroleads once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan