Redis Iris interactive demo

Step through one agent request across Intent Router, Agent Playbooks, Agent Memory, and Context Gateway, then take a service away to see what the agent loses.

Redis Iris gives an AI agent routing, governed access to live business data, memory, and approved answers. This tour follows one customer request through four services, one step at a time, in the order described in How Redis Iris works. Lens then shows how the request ran. The last step takes one service away to show what the agent loses without it.

The tour runs in your browser and doesn't connect to any service. Each step links to that service's docs or its own interactive demo, which covers it in depth. The agent's reasoning, the reply, and the timings are illustrative.

What each service adds

Service What it does in this request Without it
Intent Router Matches the message to the reorder and delivery_fee intents in milliseconds, without a model call The reply is the same, but a model call has to work out what the customer wants first, which adds time and tokens
Context Gateway Looks up delivery times, alternatives, and past orders through governed tools The agent can't check whether the food will arrive in time
Agent Memory Recalls last week's order and the customer's peanut allergy The agent can find the order, but not the allergy
Agent Playbooks Answers the general delivery fee question with the frequently asked question (FAQ) the support team published The model doesn't know the app's fees, so it gives a vague answer, or makes one up

Lens and Agent Mesh are in beta, and neither changes the reply. Lens records each step of the request, including which memories entered the prompt, so you can see how the agent got there. Agent Mesh isn't part of the tour. It keeps a long agent response deliverable when the client disconnects, so the client can reconnect and receive the updates it missed.

Next steps

RATE THIS PAGE
Back to top ↑