Head to head · Recruiting · October 2026 research run

Greenhouse vs Zoho Recruit

Greenhouse scores 59.8 (C) on agent readiness against Zoho Recruit's 55.1 (C), and leads in 5 of 7 scored categories. Zoho Recruit leads on payments & pricing. Both do recruiting.

Best recruiting and applicant tracking systems for AI agents · All 106 recruiting comparisons

Which one, for what

Greenhouse C

Best for An agent working inside a company that already runs hiring on Greenhouse and needs to read pipelines, move applications, schedule interviews or draft offer records under scoped OAuth.

Ahead on

  • Reliability, 76 against 56
  • Schema & documentation, 79 against 46
  • Security & auth, 85 against 65
  • Maintenance & community, 65 against 48

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No public price, free tier or trial. Pricing is customised through sales, and the sandbox comes only with the Pro tier

Zoho Recruit C

Best for Small businesses and staffing agencies on Zoho that want an agent to read and write candidates, job openings, applications and interviews with narrow scopes, and teams that want a free edition with API access.

Ahead on

  • Payments & pricing, 30 against 0

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Greenhouse loses 6 points for them

Watch for

No OpenAPI description found. The public repository zoho/recruit-oas still has no commits

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Greenhouse +33

Greenhouse 79

Every v3 reference page has a Markdown twin with an OpenAPI 3.1 definition for that endpoint. No single downloadable spec was found (20). llms.txt indexes 179 reference pages and the guides, all served as Markdown (10). Descriptions state purpose, required fields and limits, for example that stage moves are not handled by the update call and that from_stage_id guards against stale moves (16). Request bodies set additionalProperties to false with required fields, enums and length limits (13). Success examples are given, but reference pages list 401, 403 and 422 without bodies, and error bodies appear only in the guides (8). The path is versioned and the changelog had 28 entries from 1 October to 29 October 2026, titled by commit hash with relative dates on the page, though each entry now names the endpoints and the change (12).

Zoho Recruit 46

No OpenAPI description found, and the public repository zoho/recruit-oas has no commits (0 of 25). The developer guide has an llms.txt index of 77 pages (79 recorded on 8 October), each with a Markdown twin (10). Each endpoint page states a purpose, URL, method and scopes, with little on when not to use a call (12 of 20). Parameter tables give types, defaults and possible values, and a field-type table gives length limits. Record bodies accept any field because modules are customisable, and search criteria are a string grammar (8 of 15). Pages carry curl samples, sample responses and a Possible Errors table, though the upload page's sample URL omits /v2 and the status code page is generic (11 of 15). The version is in the path. What's New in API v2 is undated, and the limits page, the What's New page and the Corporate HR plan comparison disagree on daily allowances (5 of 15).

Payments & pricing Zoho Recruit +30

Greenhouse 0

Read with the hosted rubric. No x402, MPP or L402 (0). No public prices. The pricing page names Core, Plus and Pro and says pricing is customised (0). No free tier or trial found, and the sandbox comes only with the Pro tier (0). Credentials are created by a person inside a customer account, and the MCP server's dynamic client registration still needs a paying organisation and a user's consent in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Zoho Recruit 30

No x402, MPP or L402 (0). The pricing page and its Markdown twin name the editions, and the pricing page and the plan comparison name the per-licence monthly and yearly billing and an API call add-on sold per 250 calls, but every amount is filled in by script from a price data file, which this run doesn't read. The 8 October figures came from that file and are struck, so no price could be read (0 of 20). The Free edition includes 5,000 API credits a day, and the home page says no credit card is required (20). A person signs up in a browser, registers an OAuth client in the API console and approves scopes (0). 0 + 0 + 20 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Reliability Greenhouse +20

Greenhouse 76

Read with the hosted rubric, for the Harvest v3 API. Statuspage at status.greenhouse.io with a Greenhouse Harvest API component and per-silo components (20). The history feed (history.atom) covers the 90 days from 4 August to 2 November 2026. Three posts touch the API, each partial. On 5 August a partial disruption of Greenhouse Recruiting (scorecards, notes, emails, offer letters and more) ran from 02:18 UTC to a fix at 03:56. On 2 September a HarvestV3 maintenance posted as it began gave elevated 401 errors for 34 minutes. On 13 October a partial disruption of Greenhouse Recruiting ran from 15:32 to 19:00. The rest name job boards, integrations, Voice AI or MyGreenhouse. Partial incidents only, so minor (20). The v3 limit is a fixed 30-second window whose size arrives in X-RateLimit-Limit, with no number published beyond an example of 75 (8). 429 carries Retry-After and the docs give backoff guidance, but no idempotency keys were found for writes (10). The SLA commits to 99.5 per cent for Greenhouse Recruiting with service credits and does not name the API (8). Harvest v3 is generally available, while the MCP server is in open beta (10). 20+20+8+10+8+10 = 76.

Zoho Recruit 56

Graded on the REST API v2, read as a hosted service. status.zoho.com redirects to us.zohostatus.com, which listed a Zoho Recruit component per the 8 October check (20, kept as on the other Zoho listings). On 4 November that host answered our robots.txt request with a 404 carrying an access-denied error page, read as blocked as on zoho-books and zoho-zeptomail, so the 8 October incident reading is struck and no incident history for the last 90 days could be read (5). Daily credits per rolling 24 hours and concurrency limits are published with numbers per edition (15). 429 is documented for the daily and concurrency limits, with no Retry-After or backoff guidance found. Upsert on duplicate check fields makes creates safer to retry (6 of 15). No SLA found (0). v2 is the current documented version (10). 20 + 5 + 15 + 6 + 0 + 10 = 56.

Security & auth Greenhouse +20

Greenhouse 85

OAuth 2.0 with a scope per endpoint, client credentials or the authorisation code grant, one-hour partner access tokens and secret rotation that keeps the old secret for up to a week. The MCP server adds PKCE and dynamic client registration (30). Read-only access is possible by scope, the MCP defaults to seven read-only scopes, blocks every DELETE and asks for confirmation on five actions. All list endpoints need a Site Admin as the authorising user (16). The MCP security FAQ covers prompt injection (structured tool calls only, permission-bound and rate-limited), with no guidance on treating candidate text in responses as untrusted (9). The Audit Log API records Harvest and MCP calls with user, client and arguments for thirty days, as a paid add-on (12). SOC 2 Type II, ISO 27001, 27701 and 42001, a HackerOne bug bounty and annual penetration tests. security.txt expired on 1 February 2026 (18).

Zoho Recruit 65

OAuth 2.0 with scopes down to one module and one operation, one-hour access tokens and revocable refresh tokens (30). Less 10 because the documented refresh and revoke calls carry the refresh token and client secret in the URL query string (20 of 30). READ-only scopes per module, and calls are bound by the user's profile (the Notes module answers admins only). No approval step for deletes, which take 100 records a call (13 of 20). Candidate records and résumés hold text from outside parties and no prompt-injection guidance was found (3 of 15). Audit logs kept 60 days and activity logs 90 days per the shared responsibility page, per the 8 October check, not re-read on 4 November. No per-application API usage view was found in the reviewed pages (9 of 15). security.txt valid to 30 June 2028 (re-read 4 November), a bug bounty, SOC 2 Type 2 and ISO/IEC 27001, 27701, 27017 and 27018 (20).

Maintenance & community Greenhouse +17

Greenhouse 65

The newest Harvest v3 changelog entry is dated 29 October 2026 (d5a234aa, GET /v3/prospect_details) (30). 28 dated entries from 1 October to 29 October alone (20). Closed service with a changelog, monthly release notes that list API changes and a partner support address. Changelog entries are titled by commit hash, which makes them hard to follow (10). No official SDKs found, and the MCP server is not in the official MCP registry (0, per the 7 October check, not re-read on 2 November). No package to assess. The docs repository for the older APIs had commits up to 10 September 2026 (5, per the 7 October check, not re-read on 2 November). 30+20+10+0+5 = 65.

Zoho Recruit 48

No SDK or dated API changelog exists to date a release, and the public repository zoho/recruit-oas still has no commits. The product's What's New page is dated by month. Its newest entries are dated October 2026, between 4 and 34 days old, so not shown to be within 30 days; within 90 (20 of 30). Seven entries dated October and four dated September 2026 lie inside the window from 6 August (20). A public product changelog and a community forum on help.zoho.com, which we did not test for replies. No API changelog (8 of 25). No official SDK for the Recruit API found (0 of 15). No package or public CI to assess (0 of 10). 20 + 20 + 8 + 0 + 0 = 48. The API Markdown pages, including limits, were last modified on 1 April 2026 per their HTTP headers.

Score by category

CategoryWeightGreenhouseZoho RecruitEdge
Reliability16%7656Greenhouse +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7946Greenhouse +33
Agent ergonomics13%6364Zoho Recruit +1
Security & auth14%8565Greenhouse +20
Payments & pricing10%030Zoho Recruit +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6548Greenhouse +17
Transparency & trust7%7977Greenhouse +2
Negative events≤15-60
TotalC 59.8/100C 55.1/100

Facts side by side

FactGreenhouseZoho Recruit
KindHTTP APIHTTP API
VendorGreenhouse Software, Inc.Zoho
Hosted endpointhttps://harvest.greenhouse.io/v3no (local only)
TransportsHTTPHTTP
AuthOAuthOAuth
PricingPaidFreemium
x402nono
LicenceProprietary service under Greenhouse's Master Subscription Agreement. The docs repository for the older APIs on GitHub is Apache-2.0Proprietary service under Zoho's Terms of Service
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-29none
Terms last updated2026-02-012022-03-02
Privacy policy last updated2026-05-282025-12-22
Customer content may train modelsyesyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews3/5 (4)3/5 (4)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Greenhouse

Harvest v3 pairs per-endpoint OAuth scopes with Markdown docs that embed an OpenAPI 3.1 definition for each call, and the beta MCP server blocks every DELETE. Access needs a paying customer account with no public price or trial, and October changelog entries changed published behaviour for existing clients on the day they shipped.

Zoho Recruit

OAuth scopes narrow to one module and one operation, the docs have an llms.txt index with a Markdown page per endpoint, and the Free edition includes 5,000 API credits a day with no card. No OpenAPI description, official SDK, SLA or dated API changelog was found, and the documented token refresh puts the client secret in the URL.

Before you call either

Greenhouse

  1. Request a token from https://auth.greenhouse.io/token with client credentials, then send it as a Bearer token to https://harvest.greenhouse.io/v3. Tokens expire, so repeat on 401
  2. Put filters and per_page on the first list request only. A cursor must be the only query parameter, or the call returns 422
  3. Send the current stage as from_stage_id when moving an application. Check for an existing webhook before creating one, since a duplicate answers 409. Other writes have no idempotency key
  4. Treat a job's custom_fields entries as optional. Since 26 October 2026 fields that don't apply to the job are left out rather than returned as null
  5. Expect empty list results or 403 unless the token's user is a Site Admin, and wait for Retry-After on 429 (30-second window)

Zoho Recruit

  1. Use the api_domain returned with the token, or the regional host (recruit.zoho.com, recruit.zoho.eu, recruit.zoho.in and others). Tokens from one data centre fail on another
  2. Send Authorization: Zoho-oauthtoken <token> and refresh hourly. Put refresh parameters in the POST body, not the URL
  3. Pass fields on list calls and page with page and per_page (200 at most) until more_records is false
  4. Create through /{module_api_name}/upsert with duplicate_check_fields so a retry updates instead of duplicating
  5. Move a candidate with PUT /{module_api_name}/status, not upsert. Pass trigger: [] on writes to skip workflows, approvals and blueprints

Questions

Which is better for AI agents, Greenhouse or Zoho Recruit?

Greenhouse scores 59.8 (C) on agent readiness against Zoho Recruit's 55.1 (C), and leads in 5 of 7 scored categories. Zoho Recruit leads on payments & pricing.

Do Greenhouse and Zoho Recruit need an API key?

Both use an OAuth sign-in.

Can an agent call Greenhouse and Zoho Recruit without installing anything?

Greenhouse has a hosted endpoint at https://harvest.greenhouse.io/v3. No hosted endpoint is listed for Zoho Recruit.

Other comparisons with Greenhouse or Zoho Recruit

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.