Ashby for AI agents
Ashby is an applicant tracking system for recruiting teams, covering job postings, candidate pipelines, interviews, and offers, with reporting to help hiring teams make data-driven decisions. 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 Ashby.
Move a candidate to the next stage
Change an application's stage after an interview round with the candidate has been completed.
Add a note to a candidate's profile
Create a candidate note recording feedback from the hiring team after an interview.
Confirm before approving an offer
Approving an offer is a significant hiring decision that should require sign-off first.
125 Ashby actions, graded by risk.
Every Ashby action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
62Look things up. Allowed by default.
- ashby.list_jobsList Jobs
- ashby.list_brandList Brands
- ashby.list_usersList Users
- ashby.list_offersList Offers
- ashby.search_jobsSearch Jobs
- ashby.get_job_infoGet Job Info
- ashby.list_sourcesList Sources
- ashby.search_usersSearch Users
- ashby.get_file_infoGet File Info
- ashby.get_user_infoGet User Info
- ashby.list_approvalList Approvals
- ashby.list_openingsList Openings
- ashby.list_projectsList Projects
- ashby.get_offer_infoGet Offer Info
- ashby.list_locationsList Locations
- ashby.search_openingSearch Opening
write
54Create and change things. Allow, or ask the user first.
- ashby.create_jobCreate Job
- ashby.update_jobUpdate Job
- ashby.create_offerCreate Offer
- ashby.create_openingCreate Opening
- ashby.update_openingUpdate Opening
- ashby.add_opening_jobAdd Opening Job
- ashby.create_locationCreate Location
- ashby.create_referralCreate Referral
- ashby.create_candidateCreate Candidate
- ashby.update_candidateUpdate Candidate
- ashby.add_candidate_tagAdd Candidate Tag
- ashby.create_departmentCreate Department
- ashby.update_departmentUpdate Department
- ashby.create_applicationCreate Application
- ashby.update_applicationUpdate Application
- ashby.update_job_postingUpdate Job Posting
destructive
9Delete, cancel or archive. Ask first, or deny outright.
- ashby.archive_locationArchive Location
- ashby.archive_departmentArchive Department
- ashby.remove_opening_jobRemove Opening Job
- ashby.remove_opening_locationRemove Opening Location
- ashby.archive_interviewer_poolArchive Interviewer Pool
- ashby.remove_hiring_team_memberRemove Hiring Team Member
- ashby.remove_interviewer_pool_userRemove User from Interviewer Pool
- ashby.list_close_reasonsList Close Reasons
- ashby.list_archive_reasonsList Archive Reasons
Ashby in three steps.
- 01Your users connect AshbyThey add their Ashby api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Job” can wait for the user, and “archive Location” can be denied outright.
- 03Any agent can actYour agent calls Ashby through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('ashby', { read: 'allow', write: 'ask', // create_job destructive: 'deny', // archive_location }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Ashby connects.
Users add their Ashby 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 Ashby 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 Ashby from any agent.
Ashby and Arc0, answered.
Can I use Ashby with Claude, ChatGPT or Cursor?
Yes. Connect Ashby 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 Ashby actions you allow.
How do users connect Ashby?
Users add their Ashby 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 Ashby actions can my agent take?
125 in total: 62 read, 54 write and 9 destructive, such as “create Job”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Ashby?
Yes. Actions like “archive Location” 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 Ashby too?
Yes. The same Ashby connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Ashby into your agent.
Your users connect Ashby once, under your brand. Your agent gets 125 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan