What it costs to answer a question
Your agent answered a question about data retention this morning. Will it give the same answer this afternoon?
For a large class of questions, nobody can say, because the agent works the problem out fresh every time someone asks. How much work that takes, and whether you pay for it again on the next ask, is what separates one retrieval method from another.
Two questions arrive on the same afternoon and look equally simple. The first asks: which of your integrations support SSO? The second asks: how long do you keep customer data? Both are a single line, and both sound like something a colleague could answer in under a minute. The work behind them is not remotely comparable.
Which of your integrations support SSO? Your integrations live as structured content, each record carrying fields that describe what it supports, so the agent orients itself in your content model, writes one query against the field holding the answer, and reads the result. That gives you three steps with one source. The answer already existed in your content and the agent did nothing more than go and get it. Ask again next month and the result reflects whatever shipped in between, because the query runs against live content rather than a copy of it.
How long do you keep customer data? Retention is a policy rather than a property, so no field anywhere holds the number. The agent goes looking instead, and finds a help center article saying ninety days, a security white-paper saying thirty, and a page on the documentation site you inherited in an acquisition that gestures at industry standards and hasn't been edited in years. Three sources, three answers, and nothing to check them against.
At that point the agent has to decide which source to believe, and it will. These systems don't stop and ask. The agent weighs what it found, favors whichever source reads as most authoritative, and hands your customer a confident answer about data retention roughly two minutes and a dozen tool calls later.
Tool calls can be expensive, but what's more costly is an incorrect judgment made that no one reviewed. Nobody in legal chose ninety days, and nobody decided which source wins when two of your own documents disagree. The agent decided in the moment, based on what it happened to retrieve and in what order, and the customer who phrases the question differently tomorrow may well be told thirty. Every individual response looks fine, which is exactly what makes the problem hard to catch. It surfaces when two customers compare notes, when it reaches a support ticket, or during an audit.
None of that research has to happen while a customer waits. Someone reads the help article, the whitepaper, and the inherited documentation, notices that they disagree, and settles on thirty days with the whitepaper recorded as the source of record. The conclusion gets written down along with where it came from.
When the question arrives after that, the agent retrieves a conclusion a person already reached, with a citation attached to it. The research still happened, but it happened at build time, under review, once.
Moving the work earlier changes three things:
- Consistency. Every customer who asks gets the same answer, settled once by someone with the authority to settle it.
- Cost. A dozen round trips is a dozen round trips of tokens, repeated for every person who asks. Retrieved from a settled conclusion, the same question costs one lookup.
- Speed. An answer that took a dozen calls and two minutes to assemble comes back in the time it takes to fetch one entry.
Which of the three matters most depends on what your agent is for. An agent fielding compliance questions lives or dies on consistency. An agent handling support volume feels the token cost first. An agent that customers abandon mid-conversation needs the speed. Most production agents care about all three in different proportions, and the proportions are yours to weigh.
A settled answer is only as current as the last build, which is why the choice is not made once for an entire product. Stable facts are worth settling ahead of time. Anything that moves belongs in a live query, and most products contain both.
Both approaches are retrieval, performed by different means at different moments. Sanity Context provides four of them across two retrieval modes, and each one can do something the others cannot.