Web3 Career for AI agents
Web3 Career lists crypto and blockchain job openings, used by recruiters and candidates searching for roles in the Web3 space. 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 Web3 Career.
Search jobs by technology
Find open roles filtered by blockchain, technology, or protocol.
Search jobs by location
Find listings filtered by location or remote eligibility, a read-only search.
Review listings before sharing
Pull matching job listings for a candidate to review before applying anywhere.
1 Web3 Career actions, graded by risk.
Every Web3 Career 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.
- web3_career.list_jobsList 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.
Web3 Career in three steps.
- 01Your users connect Web3 CareerThey add their Web3 Career 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 Web3 Career through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('web3_career', { 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 Web3 Career connects.
Users add their Web3 Career 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 Web3 Career 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 Web3 Career from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Web3 Career and Arc0, answered.
Can I use Web3 Career with Claude, ChatGPT or Cursor?
Yes. Connect Web3 Career 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 Web3 Career actions you allow.
How do users connect Web3 Career?
Users add their Web3 Career 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 Web3 Career 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 Web3 Career?
Yes. Allow read actions and deny writes in the Web3 Career policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Web3 Career too?
Yes. The same Web3 Career connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Web3 Career into your agent.
Your users connect Web3 Career 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