What makes Palmyra x6 special
A notable new entry has appeared in the lineup of enterprise language models: Palmyra x6. This isn't just another model that has learned to generate text better. Its main focus is agentic tasks, where the system doesn't just reason in a vacuum but actually needs to call external tools, receive results, and act on them.
The model itself is built on the Mixture-of-Experts architecture, but the real intrigue lies elsewhere: how exactly it was fine-tuned. The authors used a technique called Anchored Supervised Fine-Tuning. And here's an unexpected twist: instead of "feeding the model millions of examples," they used just 626 verified trajectories. Each trajectory is a synthetic but validated tool-use scenario. Training ran for a single epoch with a low learning rate, and to prevent the model from losing its existing skills, it was "held" close to a frozen base version using a KL anchor. A hybrid Muon + Adam optimizer scheme was used.
It almost sounds like a contradiction: a modern LLM, massive in scale, trained on just a few hundred examples. But it was precisely this compact and careful approach that delivered a significant improvement over the previous standard model for the Writer Agent environment. It seems that in model fine-tuning, what matters isn't always the volume of data, but how accurately it reflects the desired behavior.

How anchored fine-tuning works
Breaking down the procedure step by step reveals a rather elegant chain. First, a corpus of examples is built. The data isn't collected from real traffic but synthesized to cover typical tool-use scenarios: calling a function, processing the response, refining the query, and making another call. After generation, each scenario is validated—only those that genuinely and correctly solve the given task make it into the final dataset.
Then comes the most interesting part. The model isn't just fine-tuned on these examples; it's done with an anchor. Using KL divergence, its behavior is constrained: the new version can adapt to tool-use tasks, but it isn't allowed to drift too far from the frozen base model. This somewhat resembles training a person who already knows a subject well: they're shown not every possible variation, but just a few key techniques, while being asked not to forget their existing knowledge.
The combination of "small dataset + single pass + low learning rate" looks risky, but it's precisely what allowed Palmyra x6 to integrate new scenarios cleanly without catastrophic forgetting. The hybrid Muon + Adam optimizer adds computational efficiency to the process as well.
Benchmark results
The effect of this fine-tuning is visible on public tests. On the BFCL Core benchmark, the model achieves 0.785—the best result among several recently released models it was compared against. Moreover, the model isn't strong in just one exercise: when averaging across six different benchmarks, Palmyra x6 again comes out ahead of the other models in its cohort.
Bias and safety scores are also worth noting. A sharp improvement in agentic capabilities is often accompanied by an increase in bias or unsafe responses, but that didn't happen here. On bias and safety metrics, the model either matches its competitors or pulls ahead. For enterprise use, this is fundamentally important: companies need assistants that aren't just "smart" but also well-behaved and controllable.

Why this matters for business agents
For companies building their own agents, this case is a promising signal. Fine-tuning doesn't always require multi-million datasets and weeks of compute time. Sometimes it's enough to focus on a few hundred high-quality, validated scenarios and apply a technique that keeps the model from drifting off its known behavior.
Of course, 626 trajectories don't cover every possible real-world situation. But they set the right direction: the model understands how to work with tools, and its base knowledge helps it generalize these patterns to new cases. This is especially valuable in enterprise environments, where collecting a large dataset of real agent actions is difficult due to privacy constraints and the high cost of expert annotation.
That's why Palmyra x6 should be seen not just as another update, but as a demonstration of where fine-tuning for agentic LLMs is headed. And given that the model already shows a noticeable improvement over the previous version for Writer Agent, such compact yet careful methodologies could well become the new standard for enterprise agents.




