Head to head · Recruiting · October 2026 research run

Greenhouse vs Lever

Greenhouse scores 59.8 (C) on agent readiness against Lever's 45.5 (E), and leads in 5 of 7 scored categories. Lever leads on reliability and 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

  • Schema & documentation, 79 against 22
  • Agent ergonomics, 63 against 48
  • Security & auth, 85 against 53
  • Maintenance & community, 65 against 7
  • Transparency & trust, 79 against 71

Watch for

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

Lever E

Best for An agent working inside a company that already runs Lever, for reading the pipeline, adding candidates, moving stages, writing notes and feedback and scheduling externally managed interviews.

Ahead on

  • Reliability, 85 against 76
  • Payments & pricing, 8 against 0

Also in its favour

  • No incidents deducted, where Greenhouse loses 6 points for them

Watch for

No public price, free tier or self-serve signup. OAuth apps are registered with Lever and tested against a Lever Sandbox account

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.

Maintenance & community Greenhouse +58

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.

Lever 7

The newest dated API change was on the updates page at hire.lever.co, which now answers robots.txt with a redirect to its sign-in page, so the 7 October reading (30 April 2026) is struck. The other dated sources of Lever's own were looked for. lever/postings-api's last change is a README merge on 23 April 2026, 195 days before 4 November, and lever/integrator-resources' on 27 February 2025, neither tagged (0). No dated entry in the window from 6 August (0). Closed service with no changelog readable today. The Postings README sends requests to a help-centre ticket form or the repository's issues (4). No official SDK, and no Lever-published MCP server found (0). No packages to assess. The example repository has CodeQL and dependency review workflows and was last changed in February 2025 (3). 0 + 0 + 4 + 0 + 3 = 7.

Schema & documentation Greenhouse +57

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).

Lever 22

hire.lever.co, the developer documentation host, answers robots.txt with a redirect to its sign-in page, read as a refusal, so the 7 October readings from it are struck. What remains is in Lever's GitHub repositories. No OpenAPI file found. The Postman collection in lever/integrator-resources is the only machine-readable description of the Data API, 81 requests in 24 groups, unchanged since 16 April 2021 (5, the earlier partial kept). No llms.txt, and www.lever.co/llms.txt returned 404 on 7 October (0). The Postings API README says what the API does and does not do, and when to send candidates to Lever's hosted form instead, while only 6 of the collection's 81 requests carry a description (6). The README's tables name parameters and mark the required ones without types, and the collection gives example bodies only (4). The README gives example calls and the success and error bodies, and the collection has no saved responses or error list (7). Versioned paths /v0 and /v1, but the dated updates page is struck and no other changelog was found, so the line isn't met (0). 5 + 0 + 6 + 4 + 7 + 0 = 22.

Security & auth Greenhouse +32

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).

Lever 53

hire.lever.co, the developer documentation host, answers robots.txt with a redirect to its sign-in page, read as a refusal, so the 7 October readings from it are struck, among them the scope list and the per-endpoint key settings. The example OAuth app in lever/integrator-resources runs the OAuth 2.0 authorisation code flow with requested scopes, and the Postman collection authenticates with an API key as the Basic auth username (30). The Postings API README documents its key in the key query parameter for application POSTs (-10). Scopes narrow what an OAuth app can reach, and the collection's nine DELETE requests show no confirmation step (8). Resumes, notes and application answers are written by outside parties and no prompt-injection guidance was found (3). The collection includes an Audit Events request and sends perform_as to attribute writes to a user (8). SOC 2 and ISO 27001 per the security page (re-read), and a vulnerability disclosure policy at security@employinc.com in SECURITY.md with no acknowledgement time. No bug bounty and no security.txt (14). 20 + 8 + 3 + 8 + 14 = 53.

Agent ergonomics Greenhouse +15

Greenhouse 63

per_page runs from 1 to 500 and v3 no longer embeds child records in parents, but no field selection was found (15). Cursor pagination through the Link header, with filters for ids, parent ids, status, created_at and updated_at (20). Errors return a message and an errors array that names the fault, such as a cursor combined with other parameters, though reference pages don't show them (13). No idempotency keys found. Moving an application needs the current stage as a guard, and the MCP server blocks DELETE and confirms five actions. Its tool annotations couldn't be read without an account (8). Creating a candidate needs two fields, but no official SDKs were found (7).

Lever 48

hire.lever.co, the developer documentation host, answers robots.txt with a redirect to its sign-in page, read as a refusal, so the 7 October readings from it are struck, among them field selection, expand and the Data API's pagination. The Postings API takes limit and mode, and nothing readable sizes Data API responses (5). Postings lists page with skip and limit and filter by location, commitment, team, department and level, with grouping (20). The README gives an HTTP status with a body of {ok:false, error:<string>}, with no list of codes. Kept as a partial (12). No idempotency keys. The README says candidates are merged by email address, which limits duplicate people on a retried application. Kept as a partial (5). Postings applications need only name and email, the Postman collection sends perform_as with a user id on writes, and there is no official SDK. Kept as a partial (6). 5 + 20 + 12 + 5 + 6 = 48.

Reliability Lever +9

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.

Lever 85

Graded on the hosted lines for the Data API and the Postings API. Statuspage at status.lever.co lists Integration API & Webhooks, Hire, Career Site and Visual Insights for the global and EU data centres, plus partner, sandbox and third-party groups (20). From 6 August to 4 November 2026 its history feed records four incidents. Offer letter conversion failed on 7 August (offer letters only). A 15-minute outage on 12 August caused failed page loads on hire.lever.co. 500 errors on 21 August, posted against the Hire component, had a fix within 17 minutes. A server rotation caused 504s on page loads at hire.eulever.co for 45 minutes on 25 August. Each names one function, the web app or one region, so all read as minor (20). hire.lever.co, the developer documentation host, answers robots.txt with a redirect to its sign-in page, read as a refusal, so the 7 October readings from it are struck, among them the Data API's request limits and backoff guidance. The Postings API README (cloned) limits application POSTs to 2 a second, a documented limit with a number, though no Data API limit can be read (15). The same README documents the 429 and says to queue and retry every application POST that receives one, with no Retry-After header, backoff interval or idempotency key, which is retry guidance alone (10). The SLA, re-read, commits to 99.9% uptime for all customers with automatic service credits (10). The readable docs carry no beta or preview label, and the Postman collection and README use the production /v1 and /v0 paths (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.

Payments & pricing Lever +8

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.

Lever 8

No x402, MPP or L402 (0). Pricing is by quote only (0). No free tier or trial found, and the sandbox goes only to approved partners (0). API keys and OAuth apps need a person, a customer contract or Lever's partner team. We gave 5 because the Postings API returns any customer's published jobs without a key or account (5). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.

Score by category

CategoryWeightGreenhouseLeverEdge
Reliability16%7685Lever +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7922Greenhouse +57
Agent ergonomics13%6348Greenhouse +15
Security & auth14%8553Greenhouse +32
Payments & pricing10%08Lever +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%657Greenhouse +58
Transparency & trust7%7971Greenhouse +8
Negative events≤15-60
TotalC 59.8/100E 45.5/100

Facts side by side

FactGreenhouseLever
KindHTTP APIHTTP API
VendorGreenhouse Software, Inc.Employ, Inc.
Hosted endpointhttps://harvest.greenhouse.io/v3https://api.lever.co/v1
TransportsHTTPHTTP
AuthOAuthOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under Greenhouse's Master Subscription Agreement. The docs repository for the older APIs on GitHub is Apache-2.0Proprietary service under Lever's terms of service. The postings-api and integrator-resources repositories on GitHub hold documentation and example code
Read-only variant documentednono
llms.txtyesno
Last release2026-10-292026-04-30
Terms last updated2026-02-012023-08-25
Privacy policy last updated2026-05-282023-09-25
Customer content may train modelsyesnot found in the text
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 textyes
Agent reviews3/5 (4)none

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.

Lever

Lever's status page posts per-component incidents, and a published SLA commits to 99.9 per cent uptime with automatic credits. Its developer reference now sits behind a sign-in page, leaving a 2021 Postman collection and the Postings API README as the readable docs. Access needs a customer contract or partner approval, with no public price, OpenAPI file or official SDK.

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)

Lever

  1. Send perform_as with a Lever user id on writes, as Lever's Postman collection does for feedback, files, postings and requisitions
  2. Keep Postings application POSTs under 2 a second, and queue and retry any that receive 429, or send candidates to Lever's hosted form
  3. Page Postings API lists with skip and limit, and filter by location, commitment, team, department or level
  4. Send the Postings API key only from a server. It travels in the key query parameter and can land in logs

Questions

Which is better for AI agents, Greenhouse or Lever?

Greenhouse scores 59.8 (C) on agent readiness against Lever's 45.5 (E), and leads in 5 of 7 scored categories. Lever leads on reliability and payments & pricing.

Do Greenhouse and Lever need an API key?

Greenhouse uses an OAuth sign-in. Lever takes an API key or an OAuth sign-in.

Can an agent call Greenhouse and Lever without installing anything?

Yes. Greenhouse has a hosted endpoint at https://harvest.greenhouse.io/v3 and Lever at https://api.lever.co/v1.

Other comparisons with Greenhouse or Lever

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.