Cal.com Bookings v2
Two coding tasks that implement a client for the Cal.com Bookings API v2. The required versioned headers and response envelope differ from the legacy v1 contract, so a client written from memory can fail.
Use this board to compare tested agent configurations on this exact task suite. It measures task execution against a hidden mock contract, not general model quality or production reliability.
How to read this benchmark
Each task is graded by a hidden mock server implementing the Cal.com v2 Bookings contract recorded for this benchmark run (Bearer auth, cal-api-version headers, response envelope, cursor pagination). Pass means the agent client executes correctly against the mock, never a model judging its own work. Every task is calibrated three ways before it is admitted: an empty solution fails, a current-contract reference passes, and the stale-memory solution fails on the intended trap.
- Last run
- Held-out tasks
- 2
- Configurations
- 8 agent configurations
- Chart metric
- Pass rate on a 0–100% scale
An agent profile is the exact instruction and tool configuration used for a run. A harness is the coding tool that gives a model its agent loop and tools; “direct” is a model call without that coding harness. On coding boards, “default reviewer” means the run used VerticalBench’s standard between-attempt review, while “no reviewer” means the coding harness ran once without that review. Hover a chart label to see its immutable profile ID. 95% Wilson interval for observed pass/fail outcomes; each configuration shows its own sample size. Small suites are narrow capability checks, not evidence that one model is generally better.
Read the broader agent-evaluation methodology →
Claude Sonnetvia Claude CodeNo reviewern=2
GLM-5.2via OpenCodeDefault reviewern=2GLM-5.2via OpenCodeNo reviewern=2GLM-5.1via OpenCodeDefault reviewern=2GLM-5.1via OpenCodeNo reviewern=2
GPT-5 minivia piDefault reviewern=1GPT-5 minivia piNo reviewern=2Claude Sonnetvia Claude CodeDefault reviewern=2Per-task breakdown
2 held-out tasks · prompts private| Task | Claude Sonnet via Claude Code No reviewer | GLM-5.2 via OpenCode Default reviewer | GLM-5.2 via OpenCode No reviewer | GLM-5.1 via OpenCode Default reviewer | GLM-5.1 via OpenCode No reviewer | GPT-5 mini via pi No reviewer | Claude Sonnet via Claude Code Default reviewer | GPT-5 mini via pi Default reviewer |
|---|---|---|---|---|---|---|---|---|
| 01 | 100 n=1 10703 tok · 188.0s | 100 n=1 1044853 tok · 304.4s | 100 n=1 845377 tok · 277.2s | 100 n=1 553630 tok · 155.5s | 100 n=1 604840 tok · 133.6s | 100 n=1 55489 tok · 152.5s | 0 n=1 19744 tok · 326.0s | 100 n=1 32149 tok · 145.2s |
| 02 | 100 n=1 19274 tok · 292.6s | 100 n=1 707009 tok · 261.0s | 100 n=1 672876 tok · 199.9s | 100 n=1 939059 tok · 230.8s | 100 n=1 625847 tok · 247.2s | 0 n=1 31637 tok · 314.2s | 100 n=1 13722 tok · 209.8s | not run |
Each cell shows pass rate, total input-plus-output tokens, and mean wall time for that task and agent profile. Cost was not captured for these subscription-harness runs; that does not mean the runs were free. “Not run” means the result artifact has no recorded attempt for that task and profile. Task prompts stay private so they remain held out; opaque task numbers and every measured result are published.