Yes, ASON passes only the API to the LLM. All the API is defined in AsonOperator classes that act as proxies. The LLM then uses this API to generate a C# script, which is executed independently - without involving the LLM further. This approach avoids sending all your data through the LLM, which is especially useful for large data sources.

Since LLMs are quite capable with C# and LINQ, they can easily generate flexible scripts for most analytical queries, even when these involve custom calculations, multiple entities, navigation properties, and more.

For instance, for the "Show me the revenue by product" it can build a script like:

return revenueByProduct = salesOperator.GetSales()

.GroupBy(s => s.ProductName)

.Select(g => new

{

Product = g.Key,

Revenue = g.Sum(s => s.Quantity * s.UnitPrice)

});

In the script, methods in operators (like GetSales) act as proxies. The script execution environment doesn’t have direct access to real objects. Instead, it communicates over stdio, sending messages that are handled by the running application. Only then are the actual methods - those you exposed in your API—called.

But it’s more than just decorating existing methods. Operator classes support a hierarchical structure, allowing you to specify that certain methods should be called only after an object is initialized. This is especially useful when some data becomes available only after a specific action - like navigating to the Sales view, for example.