TMCnet News
Jedify Benchmark Shows Context Graphs Cut AI Token Costs by Up to 75% While Improving SQL AccuracyNEW YORK, Aug. 26, 2026 (GLOBE NEWSWIRE) -- Jedify, the autonomous context graph for data-intensive agentic applications and workflows, today announced the findings of a new benchmark study on context graph architectures, which pre-encode business logic instead of feeding raw database schema to large language models. Among the findings: context graphs can cut AI token costs by up to 75% at enterprise scale while improving SQL generation accuracy. Jedify conducted the study using its context graph implementation. The research tested the approach against a live production data warehouse, measuring 100 business questions across three complexity tiers, each run twice for a total of 200 graded data points. The context graph architecture averaged 25,036 raw tokens per SQL generation call and answered 87% of graded runs correctly. For comparison, published research on traditional approaches that inject raw database schema into an LLM reports 50,000 to 150,000 tokens per call and 60% to 70% accuracy, while multi-agent systems built on schema injection, such as CHESS, report figures near 339,965 tokens per request. Those baseline figures come from other studies run on different schemas and question sets, not from a same-warehouse comparison. Using a Token ROI framework, which weighs both cost and answer accuracy, the researchers found the context graph approach delivered roughly 4X higher return than schema-injection approaches and roughly 18X higher than naive multi-agent pipelines. "Most of the industry treats token efficiency and cost efficiency as the same problem, but they're not," said Adi Elimelech, co-founder and CTO of Jedify, who built and ran the benchmark. "When business logic is pre-encoded into a context graph, the model isn't reasoning from scratch on every query. That's the mechanism that matters, regardless of which vendor's implementation you're looking at." Optimized Token Volume is Just One Advantage This efficiency gain also opens the door to lower-cost infrastructure. Because a context graph can narrow each query down to only the entities it needs before SQL generation, the reasoning burden on the underlying model shrinks. The study's production routing analysis suggests that roughly 85% of enterprise analytics queries can run on lower-cost, open-source models rather than high-end frontier models, without a meaningful drop in accuracy. "There's a data ownership piece to this, too," Elimelech said. "When your business logic lives in a graph you control, you're not handing a frontier model provider your entire schema and every join and filter rule on every single call." The Gap Widens at Enterprise Scale At 100-table enterprise scale, the context graph architecture tested in the study injected roughly 50% fewer tokens per SQL call than a raw schema baseline. At 200 tables, that gap exceeded 75%. See how context graph architectures can reduce token consumption by up to 75% while improving SQL accuracy—and why the efficiency gap widens as enterprise data environments grow. Download the full benchmark study and read the blog post for the methodology, production results, token ROI analysis and detailed findings behind Jedify’s research. About Jedify Contacts
|

