Can AI agents automate Ashby?

Ashby is automatable today through its public RPC API. This record is Ashby recruiting (candidates, jobs, applications, interviews, offers, and tasks), including the vendor-hosted MCP at https://mcp.ashbyhq.com/mcp/v1. It is not Greenhouse, Teamtailor, Webcruiter, or Jobbnorge. The API at https://api.ashbyhq.com is RPC-style: most endpoints are POST /CATEGORY.method with JSON bodies and Content-Type application/json. Authentication is HTTP Basic with the API key as username and a blank password. Keys carry module permissions (jobs, candidates, interviews, offers, and others). Confidential jobs and projects and non-offer private fields are off unless an admin enables those key flags. Documented writes include candidate.create, application.create, application.changeStage, candidate.createNote, and offer.create. Webhooks are configured in Admin > Integrations > Webhooks or via webhook.create, with optional HMAC signing in the Ashby-Signature header. First-party MCP is beta. An org admin must enable it under Admin > Organization Setup > Opt-in features. It is available on Foundations, Legacy, Plus, and Enterprise, not Analytics-only orgs. Auth is per-user OAuth. Tools search and filter candidates, jobs, applications, interviews, and offers, and can create a candidate, add a note, change an application stage, and consider a candidate for a job. Tool inputs may change; Ashby tells integrators who need a stable contract to use the public API. Rate limits are 120 requests per minute per token and 120 tool-budget units per minute. Official SDK, CLI, and iPaaS catalogs were not established from the opened pages. Computer-use viability is unassessed. API scores 8 and is the best path because it is the complete control plane and does not depend on the MCP beta or an org-admin opt-in.

Best path today: api · Overall automatability: 8/10