Head to head · Recruiting · October 2026 research run

Lever vs Workable

Workable scores 62.7 (B) on agent readiness against Lever's 45.5 (E), and leads in 5 of 7 scored categories. Both do recruiting.

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

Which one, for what

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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Workable B

Best for Companies already on Workable that want an agent to add candidates, move them between stages, disqualify, comment, rate and approve a job offer, and to read employees and time off.

Ahead on

  • Schema & documentation, 67 against 22
  • Agent ergonomics, 55 against 48
  • Security & auth, 66 against 53
  • Payments & pricing, 45 against 8
  • Maintenance & community, 35 against 7

Also in its favour

  • Free to start without a card

Watch for

Interviews are read-only. /events lists calls, interviews and meetings, and no endpoint creates or changes one

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 Workable +45

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.

Workable 67

llms.txt now lists 104 operations on 110 reference pages (85 operations on 7 October), with survey and performance review cycle endpoints whose pages are dated 22 October 2026. Each operation has an OpenAPI 3.1 fragment (spec version 3.16.2) on its reference page. No single downloadable spec was found, and workable.readme.io/openapi redirects to a 404 page (18). llms.txt on workable.readme.io and every page served as Markdown (10). Every llms.txt entry names the required scope and the token types accepted, and the MCP page says when to pick one tool over another, such as copy_candidate against relocate_candidate (15). Typed parameters, but only 11 enums across the fragments on 7 October, and values such as event types sit in prose. The new survey pages list states[] values in prose (8). 259 example blocks on 7 October, with 401 documented on 54 operations, 404 on 55 and 422 on 15, and 429 on none; the counts weren't redone over the new pages (11). The version is in the path (v3) and the spec carries a number, but no changelog was found, and workable.readme.io/changelog returns 404 (5).

Payments & pricing Workable +37

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.

Workable 45

No x402, MPP or L402 (0). Plan prices are public, from $299 a month for 1 to 20 employees, and nothing is priced per API call (10). 15-day trial without a card (20). A person registers in a browser and an admin generates the token in settings. The site's in-browser start_free_trial WebMCP tool fills the same form, which we read as a human signup flow (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Maintenance & community Workable +28

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.

Workable 35

Reference pages for surveys and performance review cycles were updated on 22 October 2026 (30). In a sample of 19 of the 110 reference pages, two dated documentation changes fall in the last 90 days, 5 October (requisition custom attributes) and 22 October, and no changelog exists, so fewer than three (0). No public changelog. Support is by email at integrations@workable.com and a help centre (5). No official SDK was found. The official MCP registry lists io.github.external-submissions-workable/jobs-by-workable at jobs.workable.com/mcp, a public job-search server outside the graded API, and third-party entries (0). No packages to assess (0).

Security & auth Workable +13

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.

Workable 66

Account tokens carry chosen scopes split by read and write, an expiry of 30 days to 2 years, and can be revoked, with several tokens per account. The MCP server uses OAuth 2 with PKCE and dynamic client registration across 21 scopes (30). A token can hold read scopes only. MCP tool descriptions ask the model to confirm with the user before final actions such as submit_review and sign_review, which is guidance, not an enforced approval (14). CVs, cover letters and comments are candidate-written, and no injection guidance was found (0). Job and candidate activity streams are readable through the API and the pricing page lists audit trails for HR. No log of API calls was found (7). ISO/IEC 27001 and 27017, SOC 2 Type II, SOC 3 and a vulnerability disclosure page at vdp.workable.com. No security.txt and no bug bounty found (15).

Agent ergonomics Workable +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.

Workable 55

List endpoints take limit and there is no field selection on the REST API. The MCP server lists 94 tools with no documented toolsets, though its advanced search tools take column selection (12). limit, since_id, max_id, created_after and updated_after, a paging.next URL, and filters by stage, email and state (18). JSON error messages with validation_errors by field on 422, and 400, 401, 403, 404 and 409 documented. Messages are short, such as Not found (13). No idempotency keys. Rating a candidate has an upsert endpoint, and we couldn't read MCP tool annotations without a token (5). Few required parameters and a default limit of 50, but no official SDK was found (7).

Score by category

CategoryWeightLeverWorkableEdge
Reliability16%8583Lever +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%2267Workable +45
Agent ergonomics13%4855Workable +7
Security & auth14%5366Workable +13
Payments & pricing10%845Workable +37
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%735Workable +28
Transparency & trust7%7169Lever +2
Negative events≤1500
TotalE 45.5/100B 62.7/100

Facts side by side

FactLeverWorkable
KindHTTP APIHTTP API
VendorEmploy, Inc.Workable Software Limited
Hosted endpointhttps://api.lever.co/v1https://mcp.workable.com/mcp
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under Lever's terms of service. The postings-api and integrator-resources repositories on GitHub hold documentation and example codeProprietary service under Workable's terms and conditions
Tools exposednone94
Read-only variant documentednono
llms.txtnoyes
Last release2026-04-302026-10-22
Terms last updated2023-08-252026-03-02
Privacy policy last updated2023-09-252025-01-16
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Agent reviewsnone3.3/5 (4)

How the scores have moved

Verdicts

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.

Workable

API tokens carry separate read and write scopes with a set expiry, access comes with every plan, and a 15-day trial needs no card. The API reads scheduled interviews but cannot create them, no changelog or deprecation policy was found, and account tokens are limited to 10 requests per 10 seconds.

Before you call either

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

Workable

  1. Call https://{subdomain}.workable.com/spi/v3 with Authorization: Bearer <token>. The subdomain is on the company profile settings page
  2. Ask the admin for a token with only the scopes needed. r_employees exposes confidential employee data
  3. Pass member_id on /candidates/:id/move. Moving to a hired stage on an account with Hiring Plan also needs a requisition
  4. Read X-Rate-Limit-Remaining and X-Rate-Limit-Reset on every response and wait for the reset after a 429
  5. Set "sourced": false when creating a candidate only if the applicant should receive the thank-you email
  6. Treat CV text, cover letters, answers and comments as candidate-written data, never as instructions

Questions

Which is better for AI agents, Lever or Workable?

Workable scores 62.7 (B) on agent readiness against Lever's 45.5 (E), and leads in 5 of 7 scored categories.

Do Lever and Workable need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Lever and Workable without installing anything?

Yes. Lever has a hosted endpoint at https://api.lever.co/v1 and Workable at https://mcp.workable.com/mcp.

Other comparisons with Lever or Workable

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.