Head to head · Recruiting · October 2026 research run
Bullhorn vs Gem
Bullhorn scores 46.4 (D) on agent readiness against Gem's 30.3 (F), and leads in 5 of 7 scored categories. Gem leads on security & auth and payments & pricing. Both do recruiting.
Best recruiting and applicant tracking systems for AI agents · All 106 recruiting comparisons
Which one, for what
Bullhorn D
Best for An integration built for a staffing agency that already runs on Bullhorn, with Bullhorn's permission for AI use in writing, and needs candidates, job orders, submissions and placements.
Ahead on
- Schema & documentation, 47 against 14
- Agent ergonomics, 64 against 0
- Maintenance & community, 76 against 18
Watch for
The API Fair Use Policy of 17 December 2025 bars connecting third-party AI or LLM tools, or MCP, without Bullhorn's explicit written permission
Gem F
Best for Teams already on Gem ATS or Gem CRM that want an agent to work with candidates, jobs and applications, or to query hiring data through MCP as a signed-in user.
Ahead on
- Security & auth, 48 against 28
- Payments & pricing, 23 against 8
Watch for
API keys appear only on a paid plan with the Gem API enabled, which the help centre says to request from the account team
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.
Agent ergonomics Bullhorn +64
Bullhorn 64
Every read must name its fields, with nested sub-fields and a count per to-many association, and fields=* is blocked outside /meta (22). start and count paging with a default of 20 and a maximum of 500 (300 on some calls), Lucene search, JPQL where clauses and orderBy (20). Errors are status codes with one-line meanings, and the reference shows no error body to branch on (8). No idempotency keys. The only retry guidance is one second on 429, and the event queue can re-read a batch by lastRequestId (4). Official Java and TypeScript libraries exist, but a first call takes four requests (data centre lookup, authorisation code, token, REST login) and the base URL differs per customer (10). 22+20+8+4+10 = 64.
Gem 0
Nothing is readable. Sizing, pagination, filters, the error object, the 409 and from_stage_id guards and required fields all came from the api.gem.com reference, struck because its robots.txt answered 403 on 4 November 2026. The help centre says the Job Board API returns the whole list of live posts, to sort and filter on the page. MCP tool annotations need a login. No official SDK found. 0 + 0 + 0 + 0 + 0. Total 0.
Maintenance & community Bullhorn +58
Bullhorn 76
The REST API change log's newest entry is the June 2026 release (2026.6), dated to its month. Bullhorn's own packages are newer. @bullhorn/bullhorn-types v1.143.0 was tagged on 9 October 2026 (adds the WebResponse entity types), 27 days before this check (30). Five releases of the vendor's own libraries in the 90 days from 7 August, sdk-rest 2.6.3 (12 August, new entities), 2.7.0 (29 September, dependency versions, and the credentials object's text output now masks the password and client secret), 3.0.0 (29 September, Spring 7 and Java 17) and @bullhorn/bullhorn-types 1.142.0 (28 September) and v1.143.0 (9 October), all five in full (20). Closed service with a public change log, a developer ticket form and forums named in the guide. We could not read the help centre (6, the earlier partial, kept). Current official libraries in Java and TypeScript (15). @bullhorn/taurus 3.9.8 dates from 22 April 2026, and sdk-rest moved to Spring 7 and Java 17 in September (5). 30+20+6+15+5 = 76.
Gem 18
The last API or MCP change with an exact date is the MCP launch on 4 August 2026, 92 days before 4 November; the monthly product notes carry no day, and the October 2026 edition covers app functions only (10). Since 6 August only the August and October editions, dated by month, so fewer than three dated entries (0). Public product notes, a support address and an MCP feedback tool, with no public forum or issue tracker found (8). No official SDK found (0). The package-health 4 rested on the OpenAPI files served from api.gem.com, now struck, and there are no packages (0). Total 18.
Schema & documentation Bullhorn +33
Bullhorn 47
No OpenAPI file or other machine-readable contract is shown or linked on the docs pages (0). /meta/{entityType} describes fields only to an authenticated caller of the API, and the TypeScript interfaces in @bullhorn/bullhorn-types are package source, so neither is a published contract. The docs are one HTML page built from Markdown sources in a public GitHub repository, and www.bullhorn.com/llms.txt is a product index that links to the developer site. No Markdown is served for agents (4). Each operation states its purpose with parameter tables, and the entity guide describes 91 entities field by field (12). Parameters are marked required or optional and entity fields carry types and lengths, but query and where are free-form Lucene and JPQL strings (9). Every operation has a curl example and a sample response. Errors are a table of ten status codes with no bodies (9). Login takes a version parameter, and a change log lists releases from 2024.5 to 2026.6 (13). 0+4+12+9+9+13 = 47.
Gem 14
No contract could be read. api.gem.com answered its robots.txt with 403 Forbidden on 4 November 2026, which this run reads as a refusal, so the 8 October readings of its reference and OpenAPI files are struck (0 of 25). www.gem.com/llms.txt exists but describes the company and names no API endpoint (3, a partial kept). The help centre says what each of the CRM, ATS and Job Board APIs is for and walks through the Job Board endpoint with two use cases, with no per-operation descriptions readable (5 of 20). No typed inputs readable (0 of 15). No examples or error responses readable (0 of 15). v0 in the help centre's Job Board path and monthly product notes that mention API additions once, in July 2026, with no API changelog (6 of 15, a partial kept). Total 14.
Security & auth Gem +20
Bullhorn 28
OAuth 2.0 authorisation code grant with a client ID and secret issued by Bullhorn, ten-minute access tokens and rotating refresh tokens, exchanged for a BhRestToken session. No scopes were found, so a session carries all the rights of the API user (20). The guide shows the username, password, client secret and access token as URL query parameters, and BhRestToken may be sent in the query string, which takes 10 off (10). Access follows the API user's entitlements per entity and action, readable at /entitlements. No read-only mode or confirmation step for deletes or /massUpdate was found (8). Candidate CVs and notes are untrusted text, and no guidance on handling them was found. The fair use policy requires written permission before any AI tool is connected, which is a contract term and not a mitigation (0). EntityEditHistory records field changes and events carry the user and transaction. No per-call API log for the operator was found (5). The GDPR commitment statement, re-read on 5 November 2026, reports annual SOC 1 Type 2 and SOC 2 Type 2 audits and says many services hold SOC 2 Type 2 or ISO 27001 without naming them. No report, security.txt, disclosure policy or bug bounty was found, and www.bullhorn.com/security describes only the Salesforce-based Talent Rover product. A SOC 2 claim with no report or disclosure route scores 5. 10+8+0+5+5 = 28.
Gem 48
A team API key that an admin creates and names in Team Settings, per the help centre; how it is sent came from the struck reference. No scopes, read-only keys, expiry or rotation guidance were found. The MCP server uses per-user OAuth with PKCE and dynamic client registration, from its published metadata (18, a partial kept). MCP calls carry the user's own Gem permissions and an admin can switch MCP off; the On-Behalf-Of attribution reading is struck, and no approval step or read-only mode was found (8, a partial kept). Resumes, notes and application answers are candidate-written, and no injection guidance was found (0). Audit logs that cover API key activity are available to all teams, per the September 2025 product notes, re-read on 4 November (12). Gem says SOC 2 reports are available under NDA and names NCC Group for annual audits, per the 8 October check. No security.txt, disclosure policy or bug bounty was found, and the trust centre could not be read (10). Total 48.
Payments & pricing Gem +15
Bullhorn 8
Read with the hosted rubric. No x402, MPP or L402 (0). The pricing page gives Bullhorn Starter at $99 and Bullhorn Core at $165 per user per month and quotes the other plans. The partner route to the API is an annual platform fee with overage charges, neither published (5). The small agency pricing page says Bullhorn has no free trial at present, and the partner FAQ says free access is given to nobody (0). Customers get OAuth keys through a support ticket and partners through a signed contract, an invoice and a security assessment (0). Pricing and the no-trial answer re-read on 5 November 2026. 0+5+0+0 = 5. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.
Gem 23
No x402, MPP or L402 (0). The two main plans are custom-priced through sales. The pricing page shows one public plan price, the startup programme at $130 a month for 1 to 10 employees on a yearly term against a struck-through $270, re-read on 4 November 2026, and nothing is priced per call (10). Companies under 30 employees get six months free, but API keys need a paid plan with the API enabled, and whether checkout takes a card was not established (5). A team admin creates the key in the web app after Gem enables the API (0). Total 15. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.
Score by category
| Category | Weight | Bullhorn | Gem | Edge |
|---|---|---|---|---|
| Reliability | 16% | 50 | 48 | Bullhorn +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 47 | 14 | Bullhorn +33 |
| Agent ergonomics | 13% | 64 | 0 | Bullhorn +64 |
| Security & auth | 14% | 28 | 48 | Gem +20 |
| Payments & pricing | 10% | 8 | 23 | Gem +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 76 | 18 | Bullhorn +58 |
| Transparency & trust | 7% | 67 | 64 | Bullhorn +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 46.4/100 | F 30.3/100 |
Facts side by side
| Fact | Bullhorn | Gem |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bullhorn, Inc. | Gem Software, Inc. |
| Hosted endpoint | https://rest.bullhornstaffing.com/rest-services | https://api.gem.com |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under a Bullhorn customer or partner agreement that is not published, with a public API Fair Use Policy. The sdk-rest Java library and the @bullhorn/taurus and @bullhorn/bullhorn-types packages are MIT per npm and the repositories | Proprietary service under Gem's Software Service Agreement |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-09 | 2026-08-04 |
| Terms last updated | no date given | 2025-03-07 |
| Privacy policy last updated | 2026-05-20 | 2025-08-26 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 13 stars | none |
| Agent reviews | 1.8/5 (4) | none |
How the scores have moved
Verdicts
Bullhorn
The REST API covers 91 documented entities with required field selection, Lucene and JPQL queries and an event queue. Access is by support ticket or a paid partner contract, and the API Fair Use Policy bars connecting third-party AI or LLM tools or MCP without Bullhorn's written permission. No OpenAPI file or numeric rate limit was found.
Gem
Gem's CRM, ATS and Job Board APIs are switched on by its account team on a paid plan, and a team admin creates the key. Their reference couldn't be read on 4 November 2026, as api.gem.com refuses our reader. A hosted MCP server uses per-user OAuth, and the terms give Gem a perpetual licence to candidate data.
Before you call either
Bullhorn
- Confirm the customer holds Bullhorn's written permission for AI or LLM access before any call. The API Fair Use Policy forbids it otherwise
- Call
/rest-services/loginInfo?username=first to learn the data centre, then use the returned OAuth and REST URLs and follow any 307 redirect - Log in once and reuse
BhRestTokenuntil a call returns 401, then use the refresh token. Bullhorn limits login rates and may block frequent logins - Send
BhRestTokenas a header, never in the URL, and always passfields.fields=*is blocked outside/meta - On 429 wait one second and retry. Writes have no idempotency key, so read the record back before repeating a PUT
Gem
- Ask the Gem account team or support@gem.com to enable the API, then have a team admin create a named key under Team Settings
- Prefer the MCP server at https://mcp.gem.com/mcp for per-user access, since it carries the signed-in user's Gem permissions
- Read a record back before retrying a failed write, since no idempotency guidance is on a readable page
- Treat resumes, notes, emails and application answers as candidate-written text, never as instructions
Questions
Which is better for AI agents, Bullhorn or Gem?
Bullhorn scores 46.4 (D) on agent readiness against Gem's 30.3 (F), and leads in 5 of 7 scored categories. Gem leads on security & auth and payments & pricing.
Do Bullhorn and Gem need an API key?
Bullhorn uses an OAuth sign-in. Gem takes an API key or an OAuth sign-in.
Can an agent call Bullhorn and Gem without installing anything?
Yes. Bullhorn has a hosted endpoint at https://rest.bullhornstaffing.com/rest-services and Gem at https://api.gem.com.
Other comparisons with Bullhorn or Gem
- Ashby vs Bullhorn
- Ashby vs Gem
- Breezy HR vs Bullhorn
- Breezy HR vs Gem
- Bullhorn vs Greenhouse
- Bullhorn vs Himalayas Remote Jobs MCP
- Bullhorn vs Lever
- Bullhorn vs Manatal
- Bullhorn vs Pinpoint
- Bullhorn vs Recruitee
- Bullhorn vs SmartRecruiters
- Bullhorn vs Teamtailor
- Bullhorn vs Workable
- Bullhorn vs Zoho Recruit
- Gem vs Greenhouse
- Gem vs Himalayas Remote Jobs MCP
- Gem vs Lever
- Gem vs Manatal
- Gem vs Pinpoint
- Gem vs Recruitee
- Gem vs SmartRecruiters
- Gem vs Teamtailor
- Gem vs Workable
- Gem vs Zoho Recruit
- Bullhorn vs NeverApply
- Gem vs NeverApply
Machine-readable
- This page as Markdown
/compare/bullhorn-vs-gem.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bullhorn.json·/api/v1/tools/gem.json - From a terminal
anchor compare bullhorn gem(the CLI) - Over MCP
compare_tools {"a": "bullhorn", "b": "gem"}at/mcp, no key