Agentic Index
Greenhouse vs Workable (2026)
Greenhouse last verified ·Workable last verified
Greenhouse and Workable both anchor the ATS layer, at different price points and market centers. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Greenhouse is the structured hiring platform for scaling and enterprise teams, sold by quote, while Workable starts at $299 a month on Standard, with Workable Agent metered in AI credits on top, AI sourcing over 400M+ profiles and 290+ integrations, strongest in the SMB and mid market. Choose Greenhouse for enterprise structure and rigor. Choose Workable for public pricing and fast time to hire.
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. Greenhouse and Workable are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,165 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose Greenhouse if
- Structured hiring, scorecards, and process rigor at scale is your requirement.
- Enterprise compliance and DEI reporting matter to your organization.
- You accept a sales cycle for a system of record.
Choose Workable if
- Standard at $299 a month, with a 15 day free trial, gets you moving without a sales cycle.
- AI sourcing over 400M+ profiles bundled with the ATS is valuable.
- SMB or mid market speed matters more than enterprise process depth.
| Feature | G Greenhouse |
W Workable |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
GreenhouseIntegrations & Tool Calling The integrations marketplace Greenhouse runs at integrations.greenhouse.com lists 520 integrations in four named classes, from HRIS and onboarding and job distribution to productivity and collaboration and candidate experience. It has Alliance Partner and Preferred Partner tiers and localization across more than thirty languages. These partner integrations act outward, in systems Greenhouse does not own. Job distribution publishes job posts to external boards, and HRIS and onboarding integrations push hires into the customer's HR system. E-signature, scheduled take-home tests and CLEAR ID verification each run in a third party service and return a result into the record. SMTP relay with self service custom SMTP sends through the customer's own mail infrastructure. Multi brand job boards and featured internal job posts extend the same publishing path. Sourceintegrations.greenhouse.com and greenhouse.com/pricingread 2026-09-08 |
||
|
WorkableIntegrations & Tool Calling Named systems cover every category the product touches, all available on every plan, among them job board distribution (200+), Indeed Easy Apply, Apply with LinkedIn, LinkedIn Recruiter System Connect, two way calendar sync (Gmail and Microsoft 365), Zoom, Teams and Meet, background check integration, native e-signatures and integrations, and payroll integrations, with a partner estate at partners.workable.com. These are authenticated writes into systems Workable does not own, and the direction is named in several places. Job distribution pushes a posting out to more than two hundred external boards. Two way calendar sync writes interview events into the customer's Google or Microsoft calendar and reads availability back. Self scheduled interviews create meetings in Zoom, Teams or Meet. LinkedIn Recruiter System Connect is an authenticated two way link into the customer's LinkedIn Recruiter seat. The agent acts through these, not beside them. It sends personalized emails that drive applications, chats with candidates to capture facts, and invites them to a screening call, so outbound mail and calendar bookings land in systems outside Workable, unattended and at volume. The Chrome LinkedIn profile extension is a capture path the recruiter operates, ingestion, not browser use. Workable also offers its own API and MCP server for outside callers. The job board figure is Workable's own, and the partner catalog is not listed. Sourceworkable.com/pricing feature matrix and /workable-ai agent stepsread 2026-09-12 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
GreenhouseWorkflow Orchestration A workflow engine the customer configures runs hiring across several participants. Structured stages come with interview kits, scheduling automation weighs interviewer limits, preferences and working hours, and job and offer approval chains, bulk offers and candidate self scheduling round it out, with auto reject and auto advance adding unattended branching on Plus and above. No agent runs this sequence end to end. The Job Setup Assistant and Candidate Insights Assistant, promised for Q3 2026, are still listed as upcoming, and the sourcing piece of the Orchestrated Hiring Ecosystem launched on October 15, 2026 is in closed beta. Sourcegreenhouse.com/greenhouse-latest-featuresread 2026-11-03 |
||
|
WorkableWorkflow Orchestration The pipeline runs in eight numbered steps from intake to handover. It understands the role and the ideal candidate profile, fine tunes that profile, marking must haves, disqualifiers and what appears in the job post, sources from 400M+ profiles, sends personalized emails that drive applications, chats with candidates to fill gaps and capture basic facts, scores responses, CVs and profiles against the job criteria, moves strong candidates to the shortlist or invites them to a screening call, and hands qualified candidates to the team. Step seven branches, and the last step hands over. The spec produced at step two governs every step after it, since the ideal candidate profile determines what is sourced, what is asked in the chat and how the scoring weights apply. Workable says this forces a clear statement of what is needed before the first candidate is reviewed. The flow loops back instead of running once. As candidates respond to messages, take assessments or progress through the pipeline, the agent re-evaluates them in real time, and the shortlist updates itself. A candidate can return to scoring long after first contact, so the process holds state across days and external events. Participants are distinct and the handoffs are defined. The recruiter sets the spec and can override at any point, the agent works the pipeline, the candidate is messaged and chatted with directly, and the hiring team receives the shortlist. The agent yields automatically the moment a human engages a candidate, a defined transfer of control. Obvious rejections are filtered so they do not slow the queue. Sourceworkable.com/workable-ai eight-step breakdown and FAQread 2026-09-12 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
GreenhouseTriggers & Channel Coverage Event and scheduled triggers live in the workflow layer. Auto-reject and auto-advance rules act on an application without a person touching it, stage transitions fire on pipeline movement, and scheduling automation rules run off interview state. Scheduled take-home tests and candidate interview reminders fire on a schedule, not on a click. Channels run from email automation with SMTP relay and texting to a candidate portal at MyGreenhouse with self scheduling and scheduling links. They also include internal and multi brand job boards, e-signature and configurable candidate surveys, and Greenhouse Voice AI adds a voice channel for two way structured screening interviews at the top of the funnel. None of the AI capabilities starts on an event. A user or a connected outside assistant invokes Notetaker, the Analytics Chart Agent and MCP, so the rules that fire on events are classic ATS workflow automation. Auto-reject, auto-advance, email automation and texting are on Plus and above. Sourcegreenhouse.com/pricing and /greenhouse-latest-featuresread 2026-09-08 |
||
|
WorkableTriggers & Channel Coverage Arrival is the trigger. Every applicant is read against the spec "the moment they enter," Sunday night included, instead of the batching it replaces, where applications pile up and are reviewed in batches. The worked claim is "apply at 11pm, screening call booked by 9am." That is event driven processing with no person at the trigger point. Three further event classes are named. As candidates reply to messages the agent re-evaluates them in real time, and assessment completion and pipeline progression both reopen scoring. Continuous sourcing runs on no external event at all. Passive search, outreach and follow up "run continuously" for every role, not just the senior ones, a standing background process, not a scheduled job. Follow up implies timed recontact. Channels face the candidate. Personalized email is the outbound path, a chat the agent conducts directly with candidates fills gaps and answers questions, screening call invitations land in a calendar, and texting, video interviews and assessments are available as platform channels. Self scheduled interviews with two way Gmail and Microsoft 365 calendar sync close the booking loop. A careers page, jobs widget and 200 plus job boards are the inbound application channels. No conversational channel for the recruiter, such as Slack or Teams, is offered, and the outbound email and calendar writes run through the integrations. Sourceworkable.com/workable-ai operating-model sections and FAQ, with /pricing feature matrixread 2026-09-12 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
GreenhouseKnowledge Grounding & RAG The customer's whole hiring estate lives in Greenhouse as the system of record, from candidates, prospects and applications to jobs, interview kits, scorecards, feedback, offers and activity history. That corpus persists between runs, scales across a hiring organization far past any context window and stays queryable. Greenhouse MCP and the Greenhouse in Claude plugin let approved assistants query it for daily briefs, pipeline reviews and debrief preparation, Chart Builder turns plain questions into charts over the reporting data, and Notetaker writes AI notes back onto scorecard questions. The announced Candidate Insights Assistant, designed to give answers linked to sources, is still listed as upcoming. Sourcegreenhouse.com/greenhouse-latest-featuresread 2026-11-03 |
||
|
WorkableKnowledge Grounding & RAG The agent is grounded in two maintained corpora, both persistent and both queried. The external one is a standing index of more than 400 million candidate profiles ("400M+ candidate profiles", beside passive candidate sourcing), and the agent sources candidates from it as step three of its pipeline. The internal one is the customer's own estate, a talent CRM database with past candidate resurfacing, so prior applicants can be searched again instead of archived. Both stand between runs and far exceed any context window. The spec is a structured retrieval object, not a prompt. The agent builds an ideal candidate profile through a guided intake conversation, structured into matching categories Workable lists (experience level, tools and technologies, certifications, languages, domain knowledge and others), with the customer marking each as a must have, a nice to have or a disqualifier. Candidates are then evaluated against "up to 14 criteria specific to your job," each scored independently and normalized, so retrieval is matched against a specification the customer wrote, not a free text query. Grounding is continuous, since the agent re-evaluates candidates in real time as they respond to messages, take assessments or progress through the pipeline, and the shortlist updates itself. Resume parsing is automated on intake and the agent chats with candidates to fill gaps, so the corpus is actively completed, not passively read. Workable claims no document ingestion for the customer's own policy content, citation to source documents or customer facing search over its training data. Sourceworkable.com/workable-ai agent steps and FAQ, with /pricing sourcing suite featuresread 2026-09-12 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
GreenhouseMemory & State Persistence Greenhouse names no agent memory layer, no state its AI keeps across sessions and no retained preferences. Candidates and applications, scorecards and notes, offers and activity history persist in Greenhouse as the application's own data model, and deleting them deletes the hiring record itself. Notetaker transcribes an interview, the Chart Agent answers a question and MCP serves a query, and Greenhouse does not say that any of them retains anything between invocations. The Pro tier's data configuration controls cover session time-outs, restricted files and application limits, with no retention or deletion control over agent memory. Sourcegreenhouse.com/greenhouse-latest-features, /security and /pricingread 2026-09-08 |
||
|
WorkableMemory & State Persistence Three things could look like agent memory, and none is. The ATS is the system of record. Workable holds a talent CRM database, candidate profiles, scorecards, pipelines, interview kits, employee records and role history, and the agent reads all of it on every run. That is the customer's application data, persistent because it is a database, in the same way a CRM or an ERP is persistent, and it serves as the knowledge corpus the agent queries. The ideal candidate profile is configuration, not accumulation. It is authored once through a guided intake conversation, with the customer marking must haves and disqualifiers, and it governs the run thereafter. Reevaluation as candidates respond is the agent rereading current facts against that fixed spec, which is state within a run. Learning from outcomes is absorbed into the model. Workable's AI tools are "trained using implicit or explicit feedback from daily user interactions and analyzing why candidates are hired or moved through the hiring stages," with customer data used to enhance the performance and accuracy of its in house systems. Workable does not say this learning is scoped per customer, inspectable or reapplied as context it can recall. There is no named memory component, no retained recruiter preference or correction the agent reapplies to the next requisition, no decision trace carried between roles, no stated scope or lifetime, and no surface to inspect, edit, export or purge agent state separately from the candidate records. The site is detailed enough to list audit trails and data retention rules and never mentions memory. Sourceworkable.com/workable-ai FAQ and /pricing feature matrixread 2026-09-12 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
GreenhouseHuman Oversight & Guardrails Greenhouse's MCP server holds five high stakes actions, rejecting or hiring an applicant, merging or anonymizing candidates and bulk revoking user permissions, and returns a plain language summary that a person must confirm before the action runs. Site Admins choose which data categories outside AI tools may read or write, every delete endpoint is blocked, and each tool acts under the user's own permissions. Greenhouse says its own AI never advances or rejects a candidate, and Voice AI scores can be overridden, though rule based auto advance and auto reject run without a confirmation step. Sourcesupport.greenhouse.io/hc/en-us/articles/53944054829083-greenhouse-mcp-security-faqread 2026-11-03 |
||
|
WorkableHuman Oversight & Guardrails Workable's oversight model has its own section, headed "You stay in control," with three mechanisms named separately. The first is configurable autonomy, "Configure the agent per account, per job, and per candidate. Set sourcing parameters, screening thresholds, engagement rules, and scoring weights. Change any setting in seconds." The customer decides what the agent may do, at three levels of granularity. The second is reversibility with a stop condition, "Every action, from sourcing to engagement, is logged and reversible. The agent stops the moment you engage a candidate. Review, override or reject any decision instantly." The third is a global off switch, "Disable the agent across your entire account at any time. No downside. Your existing candidate data, scorecards, and pipelines stay intact." The stop condition does the most work, since the agent yields automatically when a human enters the conversation, so the handover is a property of the system, not a discipline the recruiter has to maintain. A confidence threshold also routes to a person, since low confidence inferences pass to a human, so uncertainty escalates by design. The scope of autonomy is itself elective, since the customer chooses what the agent does among sourcing, outreach, scoring and auto advance. The decision boundary is stated too. Recruiters still own the relationship and the final call, and the agent hands over a shortlist ready for interview, not hiring decisions. Workable also says customers keep human oversight at every step as part of its EU AI Act alignment, so oversight underpins its own regulatory position. Sourceworkable.com/workable-ai control and compliance sectionsread 2026-09-12 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
GreenhouseSecurity, Identity & Governance Annual third party audits cover SOC 1 Type 2 and SOC 2 Type 2, and Greenhouse holds ISO 27001:2022, ISO 27701:2019 and ISO 42001:2023 certificates. It cites GDPR, CCPA and CPRA and the EU-U.S. DPF with its UK and Swiss extensions, and its trust center describes PCI DSS compliance through a self assessment. Single sign on comes with every tier, alongside SCIM provisioning, granular permissions and permissions approvals, and the audit log is Pro only. MCP access is set by Site Admins per data category and runs under each user's own role. Sourcegreenhouse.com/securityread 2026-11-03 |
||
|
WorkableSecurity, Identity & Governance Workable holds four attestations, publishes two of the certificates as downloads, and links Security from the footer of every page. It is certified with ISO 27001 for its information security management system and ISO 27017 for security controls in the provision and use of cloud services, publishing the certificate PDF for each, holds SOC 2 Type II covering Security, Availability and Confidentiality, with the report available through an account manager, and publishes a SOC 3 report openly. The AI product page repeats the set, "We hold ISO 27001, ISO 27017, and SOC 2 Type II certifications." ISO 27017 is the cloud specific standard and a narrower, more informative claim than a general ISMS badge. Customers get named controls, with single sign on on every plan and its own help article, advanced access controls, custom user permissions and additional permission sets in the ATS, audit trails in the HR features, and candidate data retention rules with automatic deletion when a retention period expires. A web application firewall sits above the cloud providers' own controls, security logs are analyzed for abnormalities, third party technical security assessments are commissioned and internal red teaming is run. Governance at the agent level is separate and granular. The Agent is configurable per account, per job and per candidate, with an admin kill switch that disables it across the entire account at any time, leaving existing data, scorecards and pipelines intact. The privacy program is a product, not a policy. A Data Protection Officer is appointed, GDPR automation tools let a customer exercise a candidate's correction, deletion and access rights from the platform, consent is captured by default on every Workable generated application form, and EEO, OFCCP, CCPA and CPRA compliance features are listed. Sourcehelp.workable.com security and data privacy article, with /workable-ai and /pricing feature listsread 2026-09-12 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
GreenhouseObservability & Auditability An audit log ships on Pro, with an Audit Log API, and gives a retrievable record of user and system activity. Greenhouse's MCP documentation covers audit logging of MCP activity for customers who have the audit log, but Greenhouse does not say the log captures the prompts, inputs or reasoning behind an AI action, and customers without it have no such record. Reports, dashboards, AI report filters and the BI Connector measure hiring operations, not agent behavior. Sourcegreenhouse.com/securityread 2026-11-03 |
||
|
WorkableObservability & Auditability Workable offers both an action log and an explanation layer, under a heading that names the standard. A section titled "Transparent, not black box" reads "Every score has reasoning. Every candidate action is logged. You can audit exactly why the agent did what it did." Every action, from sourcing to engagement, is also logged and reversible. The scoring is broken down, not opaque. The agent evaluates against up to fourteen job specific criteria, each scored independently and then normalized to a 0 to 100 scale, and "you see the score for each criterion, plus the overall score." A reader can see not only that a candidate scored 62 but which of the fourteen criteria produced it. That answers why this candidate, and the action log answers what the agent did. Audit trails are a named platform feature beyond the agent, listed in the HR information system feature set, alongside a full reporting suite and a custom report builder on every plan. Data export is an ATS feature, so the record can leave the system. Workable ties explainability to its EU AI Act alignment and says it is committed to making its AI functionality as transparent and explainable as possible, so the audit surface underwrites its own compliance claim. Sourceworkable.com/workable-ai transparency and control sections, with /pricing feature matrixread 2026-09-12 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
GreenhouseDeployment & Data Residency Greenhouse runs on Amazon Web Services and describes no region list, regional hosting choice, VPC, on premises install or customer tenant, so a customer cannot select where its data sits. Cross border transfers rely on the EU-U.S. Data Privacy Framework and its UK and Swiss extensions, which are legal transfer mechanisms rather than a choice of location. Sourcegreenhouse.com/securityread 2026-11-03 |
||
|
WorkableDeployment & Data Residency Cloud providers are named, regions are not. Workable's top level cloud providers are Google and AWS, so infrastructure is disclosed at provider level and stops there. There is no published data center location, region list, residency election or customer hosted option, so this is plain multi tenant SaaS with no named region, customer environment or selection surface. The absence stands out against a surface that itemizes everything else. Plans list roughly seventy named features across recruiting, HR and time and attendance, down to auto fill resume applications, org chart generation and multi currency support. They include multi entity and multi currency support, which are organizational and financial structure, not data location, and carry no region, residency or hosting row at any tier, Enterprise included. Nine native language options are listed and no hosting region, which suggests region is not a choice on offer. This matters for this vendor in particular. Workable is a UK registered company with a heavily European customer base named on its AI page (Decathlon, Debenhams, Starling Bank, Boohoo, Grecotel, Korres, Ogilvy), holds ISO 27017 for cloud security controls, publishes GDPR and UK GDPR automation tooling, and states its agent is aligned with the EU AI Act. It processes candidate personal data at scale for those customers and publishes no residency position. A customer with an EU localization obligation has nothing on the site to work from. Sourcehelp.workable.com security and data privacy article, with /pricing feature matrixread 2026-09-12 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
GreenhousePrebuilt Agents, Templates & Packs Several separately named AI capabilities ship. Notetaker records and transcribes interviews and maps notes onto scorecard questions, Real Talent adds matching, fraud and spam detection and CLEAR identity checks, Chart Builder is in open beta, and Greenhouse MCP serves Site Admins. Greenhouse Voice AI, from the May 2026 Ezra AI Labs acquisition, is sold on its own with or without the ATS. Inside the ATS the capabilities come bundled by tier rather than as a set the customer picks from, there is no catalog of agents or templates to clone, and the Job Setup Assistant and Candidate Insights Assistant are still upcoming. Sourcegreenhouse.com/pricingread 2026-11-03 |
||
|
WorkablePrebuilt Agents, Templates & Packs One agent ships, not a set of agents to choose among. The agent is a single eight step pipeline that understands the role, fine tunes the ideal candidate profile, sources from 400M+ profiles, sends personalized emails, chats to fill gaps, scores against the criteria, moves strong candidates to the shortlist or invites them to a screening call, and hands over to the team. Sourcing is step three and scoring is step six of that sequence, not separate products. Workable's framing is singular, the Workable Agent, sold as one add on line item on every plan. Sourcing does not stand alone as a product without the screening step, and a customer does not choose the scoring agent over the outreach agent. Still, the agent ships prebuilt and needs no build step, the job brief capability is available to every Workable Recruiting account, not only to add on buyers, and reusable artifacts sit around it (interview kits and scorecards, offer letter templates, custom hiring pipelines, standardized evaluation tools and custom application forms), all included. Those are templates a customer selects and reuses, even though the customer authors most of them. The add on list is a pricing structure, not a pack. Texting at $89, Video interviews at $109, Assessments at $59 and Performance and Engagement at $39 are priced modules of one platform, not working agents a customer selects among. Sourceworkable.com/workable-ai eight-step agent breakdown and /pricing feature matrixread 2026-09-12 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
GreenhouseModel Flexibility & Routing Greenhouse runs off the shelf generative models alongside its own proprietary models, and its trust center lists Anthropic and OpenAI as subprocessors. Greenhouse chooses which model serves each feature, and customers get no model picker, admin setting or way to bring their own model. Choosing Claude, ChatGPT or another assistant to connect through MCP picks the outside tool that calls Greenhouse, not the models inside Greenhouse's own AI. Sourcetrust.greenhouse.comread 2026-11-03 |
||
|
WorkableModel Flexibility & Routing The models are Workable's own, by its own account. Workable says it is committed to "developing our own in-house models," uses "proprietary systems and metadata" to enhance generative AI output, focuses on using customer data to enhance the performance and accuracy of "our in-house AI systems," and commits to self evaluating "our own in-house tools" for bias and model drift. It contrasts itself explicitly with ChatGPT and Claude as black box applications. Workable says four times that the models are its own and names no provider, so there is no model for a customer to choose. One line reads like bring your own model and is not. The homepage says "You set the operating model and the guidelines, your data stays yours, and the platform works with whatever AI you bring." Two sentences later it adds, "Access to the MCP lets your own AI plug in too." The AI a customer brings is their own assistant connecting inbound through Workable's MCP server, an extension point, not a model choice. Bringing Claude to Workable does not change the model that scores a CV against fourteen criteria. Workable discloses no routing across more than one model either, and names no provider anywhere. Sourceworkable.com/workable-ai FAQ and workable.com homepageread 2026-09-12 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
GreenhouseAPIs, SDKs & MCP Extensibility The Harvest API, now on version 3 with reference documentation at harvestdocs.greenhouse.io, lets customers and partners read and update candidates, applications, jobs and scorecards, and the older v1 and v2 versions were set for removal on August 31, 2026. Job Board, Onboarding, Ingestion, Assessment and Audit Log APIs sit alongside it, with a Business Intelligence Connector and a developer sandbox on Pro. Greenhouse MCP, built on Harvest v3 with OAuth sign in, lets approved tools such as Claude, ChatGPT, Microsoft Copilot Studio, Glean, Amazon Q and Grok read and write Greenhouse data under the user's permissions, and the Greenhouse in Claude plugin, in open beta since October 22, 2026, adds hiring skills on top. Sourcegreenhouse.com/apiread 2026-11-03 |
||
|
WorkableAPIs, SDKs & MCP Extensibility Three inbound surfaces are open to outside callers. A developer API has its own footer entry on every page, at workable.com/developers, and API access is an included feature twice, under the applicant tracking system and again under time and attendance, so it comes with every plan, not as an enterprise upsell. A partner and integrations estate runs at partners.workable.com. An MCP server rounds it out, in Workable's words "The autonomous Workable Agent runs the top of your hiring funnel, and access to the MCP lets your own AI plug in too." The MCP server stands out, since a customer's own AI can call it directly. Workable frames it as the customer's AI plugging into Workable, the inbound direction, and pairs it with the standing REST API instead of offering it in place of one. The agent acts on candidates, jobs and pipelines, so an outside caller reaches the working system, not a reporting endpoint. The endpoint list, the authentication model and the MCP tool surface are named but not listed, and no SDK is claimed. Sourceworkable.com/pricing feature matrix, workable.com homepage MCP statement and the site-wide Developer API footer linkread 2026-09-12 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
GreenhouseTesting, Debugging & Optimization A developer sandbox with sandbox sync ships on the Pro tier, so a customer can try configuration and integration changes before they reach production. Greenhouse says all Voice AI scoring can be calibrated and will improve over time, and that the customer sets the criteria for what makes a candidate great. On Talent Matching, recruiters choose which criteria to prioritize and the relative weight of each factor. Greenhouse names no holdout set, scored test cases or comparable results. A bias audit statement covers Talent Matching. Warden AI runs disparate impact analysis and demographic variable testing across ten protected classes on its own proprietary dataset, and the results go to a single public Greenhouse dashboard. The audit tests the product in general, not the customer's deployed instance on the customer's data. It is aligned to NYC LL-144, Colorado SB205 and California FEHA, which are legal mandates. Reports, dashboards, AI report filters and the BI Connector measure hiring operations, not agent behavior. Sourcegreenhouse.com/pricing, /bias-audit-statement and /greenhouse-latest-featuresread 2026-09-08 |
||
|
WorkableTesting, Debugging & Optimization Scoring and bias research could pass for evaluation, but neither puts the agent under the customer's test. The scoring is the agent's output about candidates, not a measure of the agent. Workable scores each candidate against up to fourteen criteria, normalizes to 0 to 100 and shows the breakdown for each criterion. That is a readable result about the candidate, which answers a different question from whether the agent's own behavior is under test. Bias and drift evaluation is real and is Workable's own. Workable says "we will consistently self-evaluate our own in-house tools for bias and model drift," and takes part in the AIXPERT and AutoFair research programs on AI fairness as a member of the European AI Ethics Consortium. Model drift is the right object, but it is Workable evaluating Workable inside its own development process, with no surface exposed to the customer. The customer receives the outcome, not the harness. Nothing puts a customer's change under test. There is no test environment, sandbox, dry run, holdout, A/B comparison or versioning of the ideal candidate profile. A recruiter can change screening thresholds and scoring weights in seconds, and nothing exercises that change against a known set of candidates before it starts filtering live applicants, or reports whether a spec change improved the shortlist. The one surface aimed at the agent itself, low confidence inferences routing to a person, is a runtime guardrail, a form of oversight, not a measurement. Sourceworkable.com/workable-ai FAQ and control sections, with /pricing feature matrixread 2026-09-12 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
GreenhouseBrowser & Computer Use The Prospecting Chrome plugin ships on all three tiers as part of Sourcing and CRM, alongside prospect creation and prospect pools. With it, the recruiter finds the profile and opens the page, and the plugin captures what is on it into Greenhouse. The plugin does not navigate, click or fill on its own. Greenhouse names no hosted or local browser, desktop session, or remote or local computer control. Sourcegreenhouse.com/pricingread 2026-09-08 |
||
|
WorkableBrowser & Computer Use The agent's action surface is the ATS, email and a chat, none of which is an interface it navigates. The eight steps are sourcing from Workable's own profile index, sending personalized emails, chatting with candidates, scoring against criteria and moving records between pipeline stages. Every one of those is an operation inside Workable's own product or an outbound message. Nothing reads a rendered page belonging to someone else. UI changes elsewhere do not break it. Workable's integrations are named API level connections (two way calendar sync with Gmail and Microsoft 365, Zoom, Teams and Meet, LinkedIn Recruiter System Connect, Indeed Easy Apply, background check and payroll integrations), so a third party changing its interface does not touch the agent. The Chrome extension is not browser use. A Chrome LinkedIn profile extension is included, but the recruiter opens a LinkedIn profile and the extension captures it. That is ingestion the recruiter operates. Workable has no LinkedIn send path. Its LinkedIn connections are Recruiter System Connect and Apply with LinkedIn, both sanctioned integrations. There is no hosted or local browser, desktop session, remote or local computer control, RPA or recorder, though the feature list names a mobile app and a jobs widget. Sourceworkable.com/pricing feature matrix and /workable-ai agent stepsread 2026-09-12 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | G Greenhouse |
W Workable |
|---|---|---|
|
Entry price Lowest public entry point |
Quote only | Standard $299/mo ($3,588/yr), Premier $599/mo ($7,188/yr) and Enterprise $719/mo ($8,628/yr) at the 1 to 20 employee band. Workable Agent is extra, metered in AI credits. |
|
Pricing confidence How public the numbers are |
Contact only | Public, exact |
|
Billing Primary billing axis |
A custom quote shaped by the plan, hiring volume and organizational complexity. The unit hiring volume is counted in is not defined. | Two meters, and they are independent. The platform is a monthly subscription banded by employee headcount across nine brackets, from 1 to 20 employees up to 1000+, not per seat and not per job. The Agent is an add on metered in AI credits per action it takes on a candidate, so agent cost tracks candidate volume rather than headcount. A company with 30 employees hiring heavily and one hiring rarely pay the same platform fee and very different agent bills. |
|
Variable cost Workload / overage exposure |
Medium variable cost | High variable cost |
|
Free tier / trial Try before you buy |
No free tier
|
No free tierTrial
|
|
Buying motion Self-serve vs sales call |
Sales call | Mixed |
|
Pricing verified When this pricing was last checked |
Product updates
Newest first, each linked to its source.
Greenhouse
-
· Integrations
Recruiters and hiring managers can now check pipelines, prepare for debriefs and draft scorecards inside Claude with Greenhouse in Claude, a plugin built on Greenhouse MCP.
Source -
· MCP / tool calling / API
Greenhouse expanded access to its Model Context Protocol (MCP) beyond Site Admins, enabling Job Admins, coordinators, and hiring managers to run AI workflows against platform data.
Source
Workable
-
· Agent capability
Workable made its four AI Recruiting Agents generally available for job briefing, sourcing, screening and engagement, with pay as you go credit pricing and expanded MCP support.
Source -
· MCP / tool calling / API
Workable expanded its Model Context Protocol (MCP) Server by adding 37 new tools, bringing the total to 94.
Source
More comparisons with Greenhouse or Workable
Other matchups in enterprise operations agents
Not the pairing you were after? These compare a different set of enterprise operations agents on the same 14 capabilities.