Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Preprint
Data sources: ZENODO
addClaim

Best Token Use Path (BTUP): Client-Side Traffic Engineering for Cost-Aware LLM Inference

Authors: Trama, Francesco;

Best Token Use Path (BTUP): Client-Side Traffic Engineering for Cost-Aware LLM Inference

Abstract

Large language models select generation behavior against a trained quality objective that contains no representation of token cost — the inference analogue of a link-state routing protocol whose advertisements omit the cost field. Every path looks free, so the protocol systematically prefers verbose, expensive routes: preamble, restatement, hedging, full-file rewrites, and unbounded agent loops. Prior work attacks components of this problem — model cascades and routing, prompt compression, reasoning budgets, length control — but treats each as an isolated optimization. We introduce Best Token Use Path (BTUP): a provider-independent, client-side traffic-engineering framework that represents an AI request as a complete execution path (context policy, retrieval, prompt transform, cache strategy, provider/model, reasoning and output budgets, output contract, tool plan, validation, and retry/escalation policy) and selects the path minimizing expected cost per accepted resolution (CAR) subject to quality, latency, safety, privacy, and budget constraints. We specify the control plane — edge classification, service-class policy, a Path State Database, constrained path computation, validator-driven fast reroute — together with a provider-accounting reconciliation model, privacy-preserving telemetry, and a security model covering denial-of-wallet, tool-loop containment, and refusal handling. We describe a production implementation; empirical results from live traffic will be reported in a subsequent version of this paper. We argue the methodology grows in importance regardless of price direction, because agentic workloads multiply tokens-per-task faster than unit prices decline.

Powered by OpenAIRE graph
Found an issue? Give us feedback