Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ You also need a shell with `curl` and `jq` installed.
## Save the connection values

1. Open the Redis Agent Memory service in the Redis Cloud console.
1. On the **Configuration** tab, copy the **Endpoint** and **Store ID**.
1. On the **Configuration** tab, copy the **Store ID** and the URL from the **URL List**. This URL is the endpoint.
1. Export the values for your chosen client in your shell:

{{< multitabs id="connection-values" tab1="Python" tab2="TypeScript" tab3="curl" >}}
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ See [Redis Agent Playbooks concepts]({{< relref "/develop/ai/context-engine/agen

## Get started

1. Set up a playbook. Operator guides are coming soon.
1. [Create a playbook]({{< relref "/operate/iris/agent-playbook/create-playbook" >}}) on Redis Cloud.
2. [Publish and retrieve your first FAQ]({{< relref "/develop/ai/context-engine/agent-playbooks/quickstart" >}}).

## Manage playbook entries
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -68,9 +68,7 @@ Your administrator sets the playbook controls:
| `discovery.maxResults` | `10` | Combined result ceiling for pins and discovered matches. |
| `discovery.previewTokenBudget` | Disabled | Estimated token ceiling for the discovery response. It applies only when `discovery.previewTokenBudgetEnabled` is `true`. |

Discovery has no per-request similarity override. An administrator can adjust the playbook thresholds.

<!-- TODO: Link to Agent Playbooks retrieval configuration in the operator guide when available. -->
Discovery has no per-request similarity override. An administrator can adjust the playbook thresholds in its [discovery policy]({{< relref "/operate/iris/agent-playbook/manage-playbook#discovery-policy" >}}).

### Pin required knowledge

Expand Down
4 changes: 2 additions & 2 deletions content/develop/ai/context-engine/lens/configure.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,8 +65,8 @@ Lens keys have one of three scopes:
| `read` | People and tools that read turns, in the Lens user interface (UI) or with the read application programming interface (API). |
| `full` | Both. |

Agents send their key as `IRIS_LENS_API_KEY`. The read client reads its key from `LENS_API_KEY`. Give each agent an ingest key and each reader a read key, so an agent's key can't read other agents' turns. Your administrator creates keys.
<!-- TODO: link the operator guide for creating Lens keys when it exists. -->
Agents send their key as `IRIS_LENS_API_KEY`. The read client reads its key from `LENS_API_KEY`. Give each agent an ingest key and each reader a read key, so an agent's key can't read other agents' turns. On Redis Cloud, [create keys in the console](/content/operate/iris/lens/create-lens.md#create-api-keys). Self-managed, your administrator creates them.
<!-- TODO: link the self-managed operator guide for creating Lens keys when it exists. -->

## Control content capture

Expand Down
4 changes: 2 additions & 2 deletions content/develop/ai/context-engine/lens/inspect-sessions.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,8 @@ Use the Lens user interface (UI) to find a session, open a turn, and see what ha

## Connect to Lens

Open Lens. If Lens asks for a credential, paste your read key and select **Connect**.
<!-- TODO: describe where to open Lens on Redis Cloud and self-managed when the operator pages exist. -->
Open Lens. On Redis Cloud, select **Lens** under **Iris** in the console menu; Lens uses your console sign-in. Self-managed, Lens asks for a credential: paste your read key and select **Connect**.
<!-- TODO: describe where to open Lens self-managed when the operator pages exist. -->

## Find a session

Expand Down
7 changes: 4 additions & 3 deletions content/develop/ai/context-engine/lens/quickstart.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Trace one agent turn with the Redis Iris software development kit (SDK), then fi

## Before you begin

Get these values from your administrator:
Get these values. On Redis Cloud, [create Lens and its keys](/content/operate/iris/lens/create-lens.md). Self-managed, get them from your administrator.

- The Iris host, such as `https://iris.example.com`. The SDK sends turns there, and the read client reads them back from there.
- An ingest key, for sending turns.
Expand All @@ -33,6 +33,7 @@ python -m venv .venv
source .venv/bin/activate
python -m pip install redis-iris 'redis-agent-lens>=0.1.0a4'
```
<!-- TODO: confirm the install command; the console uses pip install --pre "redis-iris[llm-tracing]" -->

## Configure the SDK

Expand Down Expand Up @@ -74,8 +75,8 @@ A turn is readable a few seconds after its export.

To view it in Lens:

1. Open Lens. If Lens asks for a credential, paste your read key and select **Connect**.
<!-- TODO: describe where to open Lens on Redis Cloud and self-managed when the operator pages exist. -->
1. Open Lens. On Redis Cloud, select **Lens** under **Iris** in the console menu; Lens uses your console sign-in. Self-managed, Lens asks for a credential: paste your read key and select **Connect**.
<!-- TODO: describe where to open Lens self-managed when the operator pages exist. -->
1. Select the `lens-quickstart` agent.
1. Select the session that matches the printed session ID.
1. Expand the turn.
Expand Down
9 changes: 4 additions & 5 deletions content/embeds/rc-agent-memory-quickstart-create-service.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,6 @@
1. Sign in to the [Redis Cloud console](https://cloud.redis.io/).
1. Select **Agent Memory** from the navigation menu.
1. If Redis Cloud displays service terms, review and accept them.
1. Select **Create custom service**.
1. Select **Agent Memory** under **Iris** in the navigation menu.
1. Select **Create Agent Memory service**, or **New service** if you already have a service. Then select **Customize settings**.
1. Enter a service name, select an eligible database, and select its `default` user.
1. Under **Memory configuration**, enter these values:

Expand All @@ -12,9 +11,9 @@
| **Extraction cadence** | `1` minute | How often session events are processed for extraction. One minute is for this quickstart; use a longer production interval unless you need rapid extraction. |

1. Select **Create**.
1. Copy the Redis Agent Memory API key and store it securely.
1. On the service's **Configuration** tab, select **Create API key** and [create a key](/content/operate/iris/agent-memory/create-service.md#connect-and-create-an-api-key) with access to the service. Copy the key and store it securely.

> [!WARNING]
> Redis Cloud displays the Redis Agent Memory API key only once. If you lose it, [generate a new API key]({{< relref "/operate/iris/agent-memory/view-service#replace-service-api-key" >}}).
> Redis Cloud displays the API key's token only once. If you lose it, create a new key.

The one-minute extraction interval makes the result easier to observe in this example. For screenshots and configuration details, see [create a Redis Agent Memory service]({{< relref "/operate/iris/agent-memory/create-service" >}}).
13 changes: 9 additions & 4 deletions content/operate/iris/_index.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Redis Iris context engine
description: Deploy and operate Redis Iris context engine services.
description: Create, deploy, and operate Redis Iris context engine services on Redis Cloud or your own infrastructure.
linkTitle: Redis Iris context engine
alwaysopen: false
categories:
Expand All @@ -11,25 +11,30 @@ hideListLinks: true
weight: 45
---

Redis Iris context engine provides managed and self-managed services for building AI applications with persistent memory, semantic caching, and governed access to business data.
Redis Iris context engine provides managed and self-managed services that give AI agents persistent memory, answers and procedures your business approved, governed access to business data, and turn-by-turn tracing.

Use this section to deploy, configure, and operate Redis Iris services. Developer guides and API integration documentation remain under [Develop with Redis]({{< relref "/develop/ai/context-engine" >}}).

<div class="grid grid-cols-1 md:grid-cols-3 gap-6 my-8">
{{< tile-card icon="images/dev/icons/icon-redis-agent-memory-64-duotone.png" title="Redis Agent Memory" description="Create and manage a service on Redis Cloud or deploy it on your own infrastructure" url="/operate/iris/agent-memory" >}}
{{< tile-card icon="images/dev/icons/icon-redis-iris-64-duotone.png" title="Redis Context Gateway" description="Deploy one MCP endpoint for your agents' tools on your own infrastructure" url="/operate/iris/context-gateway" >}}
{{< tile-card icon="images/dev/icons/icon-redis-iris-64-duotone.png" title="Redis Agent Playbooks" description="Create a playbook of approved answers and procedures on Redis Cloud" url="/operate/iris/agent-playbook" >}}
{{< tile-card icon="images/dev/icons/icon-redis-iris-64-duotone.png" title="Redis Context Gateway" description="Create one MCP endpoint for your agents' tools on Redis Cloud or your own infrastructure" url="/operate/iris/context-gateway" >}}
{{< tile-card icon="images/dev/icons/icon-redis-iris-64-duotone.png" title="Redis Intent Router" description="Deploy a service that classifies requests into intents on your own infrastructure" url="/operate/iris/intent-router" >}}
{{< tile-card icon="images/dev/icons/icon-redis-iris-64-duotone.png" title="Lens" description="Trace your agents' turns on Redis Cloud" url="/operate/iris/lens" >}}
</div>

## Deployment options

Redis Iris services are available as managed services on Redis Cloud. All Redis Iris services are also available for self-managed deployment.
Redis Iris services are available as managed services on Redis Cloud. Agent Memory and Context Gateway are also available for self-managed deployment.

### Redis Cloud

Create and manage Redis Iris services through the Redis Cloud console without deploying the supporting infrastructure yourself.

- [Create a Redis Agent Memory service]({{< relref "/operate/iris/agent-memory/create-service" >}})
- [Create a Redis Agent Playbooks playbook]({{< relref "/operate/iris/agent-playbook/create-playbook" >}})
- [Create a Redis Context Gateway]({{< relref "/operate/iris/context-gateway/create-gateway" >}})
- [Create Lens]({{< relref "/operate/iris/lens/create-lens" >}})

### Self-managed

Expand Down
3 changes: 0 additions & 3 deletions content/operate/iris/agent-memory/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,9 +13,6 @@ hideListLinks: true

Redis Agent Memory provides persistent session memory and long-term memory for AI agents and applications.

![The Agent Memory page in the Redis Cloud console, with Quick create and Create custom service options.](/images/rc/agent-memory-get-started.png)
{width="75%" class="border border-redis-pen-300 rounded-lg"}

## Deployment options

### Redis Cloud
Expand Down
Loading
Loading