Coresignal for AI agents
Coresignal provides real-time employee and company data pulled from public web sources, used for recruiting, sales, and workforce research teams. 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 Coresignal.
Look up a real-time employee profile
Look up a person's current employee profile before reaching out about a role.
Run a fast search for candidates
Run a fast search across public profiles matching a role and skill set.
Search with reasoning for a complex query
Run a reasoning-based search for a nuanced query that a simple keyword search would miss.
3 Coresignal actions, graded by risk.
Every Coresignal action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- coresignal.search_fastFast Search
- coresignal.search_with_reasoningSearch With Reasoning
- coresignal.get_real_time_employee_profileGet Real-Time Employee Profile
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.
Coresignal in three steps.
- 01Your users connect CoresignalThey add their Coresignal 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 Coresignal through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('coresignal', { 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 Coresignal connects.
Users add their Coresignal 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 Coresignal 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 Coresignal from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore web data and scraping apps.
Coresignal and Arc0, answered.
Can I use Coresignal with Claude, ChatGPT or Cursor?
Yes. Connect Coresignal 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 Coresignal actions you allow.
How do users connect Coresignal?
Users add their Coresignal 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 Coresignal actions can my agent take?
3 in total: 3 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Coresignal?
Yes. Allow read actions and deny writes in the Coresignal policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Coresignal too?
Yes. The same Coresignal connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Coresignal into your agent.
Your users connect Coresignal once, under your brand. Your agent gets 3 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan