Client bot · live data

Your live data — shown exactly, not paraphrased

When a visitor asks about catalog, price, or availability, the assistant fetches it read-only from your systems and renders it as a clean table or card right in the chat. The numbers are yours, passed straight through — never invented. A pure lookup can even skip the model entirely and render instantly.

Fetch read-only · GETHosts allowlisted per botLookups card-only = no model call

ReadyAssistant/catalog

What scissor lifts do you have and how much?

Here’s what’s in the yard right now:

Equipment	Status	Day rate
19 ft Scissor Lift	Available	$189 / day
26 ft Scissor Lift	Available	$245 / day
32 ft Scissor Lift	2 left	$310 / day
40 ft Boom Lift	On rent	$540 / day

Rendered as a tableexact

Structured results become a real table — sortable columns, monospaced figures — instead of a paragraph the model might round or reword.

ReadyAssistant

Is the 26-foot available this weekend?

26 ft Scissor LiftAVAILABLE

Day rate: $245
Weekend: Sat–Sun open

Or a compact cardcard-only

A single-item lookup renders as a card. On the card-onlypath it’s pure data — no model call, so the answer is instant and costs nothing.

How it stays honest

Read-only, allowlisted, straight through

Read-only. Data skills always fetch with GET — the assistant can look up your systems but never write to them.
Host-allowlisted. Each bot can only call the specific hosts you list; anything else is refused before the request leaves.
Numbers pass through.Figures are rendered from the fetched data, not restated by the model — so a price or a count can’t drift.
Credentials stay server-side. If a source needs auth, the bot config holds only a reference name; the secret is resolved on the server and never returned.

See the whole assistant

EyesInAI·Loading live benchmark data