|
Documentation
Book a DemoPlatform
PlatformMCPCLIAPIWorkflows
GuidesChangelog
All releases

W18 – Set glossary retrieval per call, so a stale term can't poison a batch

Max PrilutskiyMax Prilutskiy, CEO & Co-Founder·Published 18 days ago·1 min read

Glossary retrieval used to be one global setting per engine. That meant the same recall/precision tradeoff applied whether you were translating a 50-page legal doc or a button label – and the wrong setting on a single bad batch could quietly miss terms across hundreds of strings. The strategy is now per request on the async API: favor recall on long-form content, favor precision on short strings, without changing the engine config.

Also shipped#

  • Auto top-up for credits. Opt in, set a threshold, credits get purchased automatically when balance dips below it.
  • Localized balance alert emails. Notifications before a balance bottoms out.
  • ISO 5060 classification visible in triage. Each triaged job surfaces the standardized error class alongside the agent's suggestions.
  • Stuck-queued localization jobs fixed. Edge case where jobs sat queued without progressing is resolved.