What the Synthetic Vendors Resemble
An approximate map from Integration Bench's fictional vendor systems to familiar ATS, HRIS, staffing, scheduling, and hiring-software product families.
Integration Bench uses generated vendor systems so a model cannot solve a task by recalling a real API. The names, endpoints, authentication rules, pagination, faults, and documentation errors belong to the benchmark.
The public tickets cover staffing ATSs, enterprise recruiting systems, modern webhook-first ATSs, workforce management, payroll, background screening, interview scheduling, onboarding, and talent intelligence.
The current public manifest reports 14 benchmark vendors. Across the public ticket text, 15 synthetic service names appear because task-0011 pairs TalentForge with Onboardly. The table includes all 15 vendors.
Approximate vendor map
These comparisons describe product family, data model, and integration surface. They do not identify hidden source systems. Each vendor’s API was generated independently, and no synthetic vendor is intended as a copy of one named product.
| Synthetic service | Product class | Comparable real products | Evidence in the public tickets | Public tasks |
|---|---|---|---|---|
| StaffLine | Legacy staffing ATS | Candidates, jobs, applications, and notes; polling-only freshness; app-token and HMAC authentication; upstream-clock watermarks. | ||
| TalentForge | Enterprise ATS and recruiting CRM | OAuth, candidate and application records, recruiter notes, webhooks, pipeline corrections, and legal-hold exports. | ||
| Onboardly | E-signature onboarding service | Creates one onboarding packet when a placed candidate arrives from the ATS. It appears as an adjacent service in a cross-vendor task. | ||
| Placemint | Staffing placement and commercial-operations system | Placements, clients, notes, placement stages, fee corrections, account-manager activity, and finance-facing records. | ||
| Rosterly | Rota and workforce-management system | Carers, shifts, punches, case notes, leavers, cancellations, payroll export, and timezone-sensitive records. | ||
| Vettly | Background-screening platform | Subjects, checks, and reports with OAuth polling and incremental synchronization. | ||
| Bullpen | Enterprise ATS | Candidates, jobs, and applications plus a migration from a legacy static application token to OAuth client credentials. | ||
| GlobalHire | Multinational staffing-agency platform | Candidates, placements, and agencies; static API keys; offset pagination; large tenants; polling without webhooks. | ||
| TalentLoop | Event-first modern ATS | Candidates, jobs, applications, notes, scorecards, OAuth, webhooks, reconciliation polling, and writeback. | ||
| RecruitOS | Enterprise recruiting and HCM system | Requisitions, applications, warehouse exports, reporting extracts, live API migration, and enterprise reconciliation work. | ||
| HireWire | Startup-oriented ATS | Static API key, incremental candidate reads, stage patches, activity events, and fast-changing write behavior. | ||
| CrewCall | High-churn temporary-staffing marketplace | Workers, gigs, assignments, tenant rebuilds, roster snapshots, and frequent worker turnover. | ||
| Interviewly | Interview-scheduling service | OAuth backfill, reschedule writeback, confirmation webhooks, duplicate deliveries, and out-of-order events. | ||
| SourceWell | Talent CRM and skills database | People, a controlled skill vocabulary, external skill classifications, and a searchable capability index. | ||
| Paygrade | Payroll and HRIS bridge | Employees, assignments, payroll periods, writeback, deletions, and an RPC-style API rather than conventional REST. |
Each task page lists every model's score and links through to the published trajectory.
How to read the comparisons
The closest matches are the narrow adjacent systems:
- Vettly has the same broad resource graph as a background-check provider.
- Interviewly behaves like an interview scheduler.
- Paygrade exposes the employee and assignment records expected from payroll and HRIS software.
ATS comparisons are broader. Many products share the same candidate, job, application, stage, and note model:
- TalentLoop sits in the Greenhouse and Ashby family. The public tasks emphasize OAuth, webhooks, polling, and writeback across that model.
- StaffLine and GlobalHire sit closer to staffing systems. Their tasks add placements, agencies, legacy authentication, and polling-heavy synchronization.
Those likenesses are for orientation. Auth, pagination, timestamps, and documentation defects are generated for the suite, so a TalentLoop OAuth quirk should not be read as Greenhouse’s token lifetime, and a StaffLine pagination fault should not be read as Bullhorn’s. Use the table to place a ticket in a familiar product category, then read the 50 public tasks and published trajectories for what each model actually had to do.