From 84dd9c8c1f516b3792b713213681ce20132d72b0 Mon Sep 17 00:00:00 2001 From: Casper Nielsen Date: Thu, 15 Jan 2026 20:13:32 +0100 Subject: [PATCH 1/5] docs: add dapr-agents operations page with docs on Agent Metadata Schema Signed-off-by: Casper Nielsen --- .../dapr-agents/dapr-agents-operations.md | 42 +++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md diff --git a/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md b/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md new file mode 100644 index 00000000000..be722d4febc --- /dev/null +++ b/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md @@ -0,0 +1,42 @@ +--- +type: docs +title: "Operations" +linkTitle: "Operations" +weight: 80 +description: "Get started with secure and reliable operations of Dapr Agents" +aliases: + - /developing-ai/dapr-agents/dapr-agents-operations +--- + +## Operations + +### Agent Registry + +#### Agent Metadata Schema + +Dapr Agents utilizes an Agent Registry (often referenced as `agent-registry` statestore) to communicate Agent capabilities. The Agent Registry contains Agent metadata, including the agent's name, description, version and much more. + +In order to facilitate easier handling of version changes to the agent metadata, Dapr Agents supplies versioned JSON schemas. Within the [dapr agents repository] you'll find 3 types of JSON schema files: + +- [index.json](https://raw.githubusercontent.com/dapr/dapr-agents/main/schemas/agent-metadata/index.json) +- [latest.json](https://raw.githubusercontent.com/dapr/dapr-agents/main/schemas/agent-metadata/latest.json) +- `v{version}.json` + +The `index.json` can be used as a lookup table and looks like: + +``` +{ + "current_version": "0.10.7", + "schema_url": "https://raw.githubusercontent.com/dapr/dapr-agents/main/schemas/agent-metadata/v0.10.7.json", + "available_versions": [ + "v0.10.7", + "v0.10.6" + ] +} +``` + +When the agent starts up it will insert its own metadata into the supplied Agent Registry. The Agent Metadata object contains the key `schema_version` which can be used as a reference to fetch the valid schema for that agent version: + +```sh +curl -s -v "https://raw.githubusercontent.com/dapr/dapr-agents/main/schemas/agent-metadata/v$(jq -r '.schema_version' agent-metadata.json).json" +``` From 5e188ffd801058db572e70ddc1407cc7e906f59f Mon Sep 17 00:00:00 2001 From: Casper Nielsen Date: Mon, 19 Jan 2026 10:25:46 +0100 Subject: [PATCH 2/5] fix(docs): ensure non static version numbers to avoid confusion Signed-off-by: Casper Nielsen --- .../developing-ai/dapr-agents/dapr-agents-operations.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md b/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md index be722d4febc..ddcc4302a2d 100644 --- a/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md +++ b/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md @@ -26,11 +26,11 @@ The `index.json` can be used as a lookup table and looks like: ``` { - "current_version": "0.10.7", - "schema_url": "https://raw.githubusercontent.com/dapr/dapr-agents/main/schemas/agent-metadata/v0.10.7.json", + "current_version": "X.Y.Z", + "schema_url": "https://raw.githubusercontent.com/dapr/dapr-agents/main/schemas/agent-metadata/vX.Y.Z.json", "available_versions": [ - "v0.10.7", - "v0.10.6" + "vX.Y.Z", + "vA.B.C" ] } ``` From 41d7d17c2cb82cacddb1a23656ffb7111c4703b3 Mon Sep 17 00:00:00 2001 From: Casper Nielsen Date: Wed, 21 Jan 2026 10:13:33 +0100 Subject: [PATCH 3/5] Update daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md Co-authored-by: Mark Fussell Signed-off-by: Casper Nielsen --- .../en/developing-ai/dapr-agents/dapr-agents-operations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md b/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md index ddcc4302a2d..f849ed3ee47 100644 --- a/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md +++ b/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md @@ -14,7 +14,7 @@ aliases: #### Agent Metadata Schema -Dapr Agents utilizes an Agent Registry (often referenced as `agent-registry` statestore) to communicate Agent capabilities. The Agent Registry contains Agent metadata, including the agent's name, description, version and much more. +Dapr Agents utilizes an agent registry (often referenced as `agent-registry` statestore) to communicate agent capabilities. The agent registry contains agent metadata, including the agent's name, description, version and more. In order to facilitate easier handling of version changes to the agent metadata, Dapr Agents supplies versioned JSON schemas. Within the [dapr agents repository] you'll find 3 types of JSON schema files: From bcbabdd1f92322877914118ef0aea16bb2806f6c Mon Sep 17 00:00:00 2001 From: Casper Nielsen Date: Wed, 21 Jan 2026 10:13:53 +0100 Subject: [PATCH 4/5] Update daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md Co-authored-by: Mark Fussell Signed-off-by: Casper Nielsen --- .../en/developing-ai/dapr-agents/dapr-agents-operations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md b/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md index f849ed3ee47..9598d02e12c 100644 --- a/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md +++ b/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md @@ -16,7 +16,7 @@ aliases: Dapr Agents utilizes an agent registry (often referenced as `agent-registry` statestore) to communicate agent capabilities. The agent registry contains agent metadata, including the agent's name, description, version and more. -In order to facilitate easier handling of version changes to the agent metadata, Dapr Agents supplies versioned JSON schemas. Within the [dapr agents repository] you'll find 3 types of JSON schema files: +In order to facilitate easier handling of version changes to the agent metadata, Dapr Agents supplies versioned JSON schemas. Within the agents repository you'll find 3 types of JSON schema files: - [index.json](https://raw.githubusercontent.com/dapr/dapr-agents/main/schemas/agent-metadata/index.json) - [latest.json](https://raw.githubusercontent.com/dapr/dapr-agents/main/schemas/agent-metadata/latest.json) From 1535b6bc149c848f3ea5dc9ee39c83d14b009995 Mon Sep 17 00:00:00 2001 From: Casper Nielsen Date: Wed, 21 Jan 2026 10:14:28 +0100 Subject: [PATCH 5/5] Update daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md Co-authored-by: Mark Fussell Signed-off-by: Casper Nielsen --- .../en/developing-ai/dapr-agents/dapr-agents-operations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md b/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md index 9598d02e12c..ae0ed98d86e 100644 --- a/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md +++ b/daprdocs/content/en/developing-ai/dapr-agents/dapr-agents-operations.md @@ -35,7 +35,7 @@ The `index.json` can be used as a lookup table and looks like: } ``` -When the agent starts up it will insert its own metadata into the supplied Agent Registry. The Agent Metadata object contains the key `schema_version` which can be used as a reference to fetch the valid schema for that agent version: +When the agent starts up it will insert its own metadata into the supplied agent registry. The agent metadata object contains the key `schema_version` which can be used as a reference to fetch the valid schema for that agent version: ```sh curl -s -v "https://raw.githubusercontent.com/dapr/dapr-agents/main/schemas/agent-metadata/v$(jq -r '.schema_version' agent-metadata.json).json"