Skip to content

benchmarks

One method: synthetic vendors, graded from their own request logs. Integration Bench is live. Legacy Integration Bench is late 2026.

Live · rev 01

Integration Bench

14 synthetic vendors · 21 models · 1050 attempts published in full on the first 50 tasks. Applicant-tracking, HRIS and job-board integrations across polling, webhook and writeback surfaces.
Leaderboard
In authoring · Late 2026

Legacy Integration Bench

Invented vendors on older stacks: SOAP, EDI, SFTP file drops, terminal sessions, message queues. Docs that don't match the server. Score from the request log. First public set late 2026.
What is planned

How every benchmark is built

Every benchmark on this site is built the same way. A vendor is declared once and generated into a live API simulator plus the documentation an agent reads, with a budget of deliberate documentation errors. The agent receives a ticket, a starter repository and that documentation, and has to make the integration work against the live simulator.

Grading never reads the code. It checks the data that ended up in the store against a committed answer key, reads protocol discipline out of the vendor's own request log, and checks whether the integration survived the faults injected mid-run. A failed mandatory check zeroes the task. Every check is a programmatic assertion over a recorded run, so the score can be recomputed offline by anyone.

Public tasks are for development and are what these leaderboards report. Held-out tasks are the exam; nothing about them is published until a sweep is complete.