Datacurve is a YC W24 data vendor that says it supplies frontier labs with expert-sourced RL environments, long-horizon tasks, agent trajectories, SFT demonstrations and off-the-shelf datasets. It is coding-first but now also covers data science, cyber security, ML and research. Data comes from its Shipd bounty platform of vetted engineers, which has SWE, ML and data-science tracks. It publishes DeepSWE, an open (Apache-2.0) long-horizon coding benchmark used in the Artificial Analysis Coding Agent Index.
The products page lists six offerings: reinforcement learning environments (software engineering, data science, cyber security, machine learning, research), long-horizon tasks, OTS datasets, benchmarks and evals, agent trajectories, and supervised fine-tuning. Shipd.ai lists three bounty tracks: Mars (software engineering), Eris (machine learning) and Monte (data science). The exact change dates are unknown; both pages were observed on 2026-10-05.
Why it matters: Datacurve now presents itself as a multi-domain vendor of RL environments and agent data, and its contributor supply now covers ML and data-science work as well as coding.
Between 2026-06-21 and 2026-09-03 Datacurve added results for GLM 5.2, Claude Sonnet 5, GPT-5.6 Sol/Terra/Luna, Muse Spark 1.1/1.2, Grok 4.5/4.6, Kimi K3, Gemini 3.6/3.7/3.8 Flash, Claude Opus 5, Qwen 3.8 Max, DeepSeek v4 Flash/Pro and GPT-6 Astra. It also corrected pricing and re-ran Gemini models after a token-counting issue.
Why it matters: The leaderboard is actively maintained, so it is a current reference rather than a one-off release.
The GitHub API reports Apache License 2.0, a last push on 2026-08-26 and 1,793 stars (652 in the 2026-06-07 baseline, when no license was set). Tasks use the Harbor format. Since v1.1 they run through Pier, a Harbor-compatible sandbox framework with per-agent network allowlists. The date is the last push; the exact date the license was added is not known.
Why it matters: An open license and a standard Harbor/Docker task format make the benchmark easy for labs and data-ops teams to reproduce and integrate.
Talk: 'DeepSWE: A Contamination-Resistant Coding Benchmark' (17:34). The World's Fair ran June 29-July 2, 2026 in San Francisco. The date shown is the event's first day; the exact talk day is not confirmed. A StartupHub write-up of the talk is dated 2026-07-26.
Why it matters: A public talk on how the benchmark was built, useful to researchers judging its contamination resistance.
The Batch (2026-06-19) covered DeepSWE, 'developed by Datacurve', alongside other agentic tests. It reported GPT-5.5 (xhigh) at 70%, Claude Opus 4.8 at 58% and Gemini 3 Flash at 5%.
Why it matters: Coverage in a widely read research newsletter adds to the benchmark's credibility and reach.
Written by Wenqi Huang and Peter Jiang. The agent's committed git patch is now graded in a separate isolated container. Tests emit CTRF structured reports. Tasks start on a normal main branch rather than a detached HEAD, with future commits hidden. Flaky tests and dependency drift were fixed. The task set is the same 113 tasks. The changelog records the v1.1 release on 2026-06-15.
Why it matters: Isolated grading with per-test reports makes model comparisons more reproducible and makes partial-progress analysis possible.
Artificial Analysis's methodology page says Coding Agent Index v1.1 (June-July 2026) introduced DeepSWE and removed SWE-Bench-Pro-Hard-AA. Version 1.5 (September 2026, current) is an equal-weight average of DeepSWE v1.1, Terminal-Bench 4.0 and SWE-Atlas-QnA. AlphaSignal covered the switch on 2026-06-12 and reported that Claude models had recovered gold solutions from .git history on 12%+ of SWE-Bench Pro runs. The date is AlphaSignal's coverage date; the index changelog gives only the month.
Why it matters: A major independent evaluator now uses Datacurve's benchmark, which gives it standing beyond Datacurve's own claims.
The launch post 'Introducing DeepSWE' is dated 2026-05-26 and written by Wenqi Huang, Charley Lee, Leonard Tng and Serena Ge. Datacurve's research index lists it as 2026-05-18, and the GitHub repo was created 2026-05-15. The benchmark has 113 tasks across 91 repositories in 5 languages (TypeScript, Go, Python, JavaScript, Rust). Reference solutions are written from scratch, average 668 added lines and touch about 7 files. Datacurve reports a 0.3% verifier false-positive rate against 8.5% for SWE-Bench Pro, and 1.1% false negatives against 24.0%. At launch GPT-5.5 scored 70% and Claude Opus 4.7 scored 54%. All of these figures are self-reported.
Why it matters: This is Datacurve's first major public research artifact. It is a contamination-resistant coding eval that separates frontier models more widely than SWE-bench, and it shows the kind of task authoring Datacurve sells.