Ask without landing.
Live Read is the second lane beside ingestion. The agent asks, Datris runs the same governed pipeline, and the validated rows come straight back. Nothing is written, nothing new becomes a system of record, and the agent still never holds a key.
How it works
You tell the Assistant what you want to know and that you do not need to keep it. It generates the tap, runs data quality rules and the transformation chain, and instead of a loader writing to a table, the result is held briefly so you can page through it, then it expires.
"What did FRED publish for the 10-year yield this week? I just want to see it, don't keep it."
The Assistant picks Live Read on its own when a question is one-off, and agents get the same lane through the MCP server. If the rows turn out to be worth keeping, ask for them to land in a real store: the tap, its schedule, and its incremental cursor stay put. Full reference in the docs.
Not every answer needs a table
Most of what an agent asks for is a one-off: what a source returns for these ids, whether today's file is clean, what a transformation would produce. Live Read runs the full governed pipeline and hands the rows back to the caller instead of landing them. If the rows turn out to be worth keeping, switch the destination. The tap, its schedule, and its sync bookmark do not move.
- The tap, generated or hand-written, with credentials brokered through Vault
- Data quality rules and the transformation chain
- Agent Policy, the audit log, and the run record
- The agent never holds a key, in either lane
The built-in Assistant picks the lane for you: a one-off question goes to Live Read, not a new table. Live Read in the docs →