APEX-SWE B
AI benchmark · Coding
- Domains
- Coding Enterprise Workflows Long-Horizon
- Tier
- B why
- Snapshot
What is APEX-SWE?
APEX-SWE measures whether frontier AI models can perform real-world software engineering work, including integration and observability tasks.
Coding mostly
“Measures AI performance on real-world software engineering tasks, from bug fixes to feature builds. Built in collaboration with Cognition.”
mercor.com/apex/ ↗
Lineage
Benchmarks this one is built on and built from: versions, subsets, extensions and the indexes that combine them.
Derived benchmarks
APEX-SWE (Inspect) extension
APEX-SWE (Terminus-2) extension
Tier B
Established: 15 or more models scored, or curated RL directories rate it.
How much stands behind a tier: usage, who backs it, a confirmed line from its own site or paper, and a clear read on X. High with three of the four, medium with two, low otherwise.
- 14 models scored
- listed with Mercor
- in curated RL directories (3 pts)
On X · unclear, low buzz, from 4 posts about APEX-SWE in the last month
Mostly Mercor's own leaderboard updates for new models like Haiku 5.5 and Mercury 3; Toptal cites it as a comparison point, with little independent discussion.
How we got to tier B
- Adoption: 14 models scored; listed with Mercor. Tier C.
- On X: unclear, low buzz. “Mostly Mercor's own leaderboard updates for new models like Haiku 5.5 and Mercury 3; Toptal cites it as a comparison point, with little independent discussion.” No move.
- In curated RL directories: 3 points, a floor of B. Raised to B.
- Confirmed: a line from its own site or paper places it.
A clear view on X moves a tier one step up or down; most entries don't move. How tiers work.
Where APEX-SWE sits
Its domain on the map, live. Hover a logo for its name; click to open it. Open it on the full map
Next: browse all benchmarks. Entry from the RL Research daily scrape of public sources, 2026-11-05 snapshot.