LocalAPI Simplification & Trace-First Rollouts
Friday product updates for December 26, 2025.
1 min read
localapirolloutstracessdk
Archive
This is historical material. Use the current Managed Research, Research Factory, and GEPA/GELO pages for product decisions.TL;DR
- LocalAPI definitions are simpler and more readable, with less boilerplate.
- Rollouts are trace-first (v3 trace + rewards), retiring canonical step/trajectory payloads.
- Docs, validators, and examples now align on LocalAPI naming and trace correlation IDs.
LocalAPI Definition Simplified
LocalAPI apps now center on a smaller core: a clear spec, explicit dataset/task info, and a trace-only rollout response. The result is fewer moving parts and a much more straightforward path to adding new LocalAPI services.
Trace-First Rollouts
Rollout responses now prioritize v3 traces and rewards. Training and evaluation pipelines read trace event history directly, removing the need to build and maintain canonical step/trajectory payloads.
Cleaner Examples & Validation
Updated examples and docs reflect the new LocalAPI shape, while validators enforce trace correlation IDs and required secrets so issues are caught early.