ZipRecruiter for AI agents
ZipRecruiter is a job search marketplace, used here to search job listings by role, location, and salary for candidates or recruiters researching the market. 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 ZipRecruiter.
Search jobs by role and location
Find open roles matching a title, location, and salary range, a read-only search.
Compare listings across companies
Pull multiple matching listings to compare pay and requirements.
Review results before recommending a role
Check listing details against a candidate's preferences before suggesting it to them.
1 ZipRecruiter actions, graded by risk.
Every ZipRecruiter 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.
- ziprecruiter.search_jobsSearch jobs
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.
ZipRecruiter in three steps.
- 01Your users connect ZipRecruiterThey add their ZipRecruiter no auth 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 ZipRecruiter through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('ziprecruiter', { 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 ZipRecruiter connects.
ZipRecruiter needs no credentials. Arc0 still applies your policies and records every call, so public tools get the same controls as private ones.
The same ZipRecruiter 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
- No auth
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use ZipRecruiter from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
ZipRecruiter and Arc0, answered.
Can I use ZipRecruiter with Claude, ChatGPT or Cursor?
Yes. Connect ZipRecruiter 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 ZipRecruiter actions you allow.
How do users connect ZipRecruiter?
ZipRecruiter needs no credentials. Arc0 still applies your policies and records every call, so public tools get the same controls as private ones.
Which ZipRecruiter 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 ZipRecruiter?
Yes. Allow read actions and deny writes in the ZipRecruiter policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call ZipRecruiter too?
Yes. The same ZipRecruiter connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug ZipRecruiter into your agent.
Your users connect ZipRecruiter 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