GITBOOK-377: change request with no subject merged in GitBook

Author: tweeddalex

SUMMARY.md

@@ -70,6 +70,31 @@
 ## 🛠️ Integrate an SDK <a href="#sdk" id="sdk"></a>
 
 * [Choosing the right SDK](sdk/understanding-sdks.md)
+* [🍏 Credo](sdk/credo/README.md)
+  * [Setup Credo Agent](sdk/credo/setup-credo-agent.md)
+  * [Decentralized Identifiers (DIDs)](sdk/credo/decentralized-identifiers-dids/README.md)
+    * [Create a DID](sdk/credo/decentralized-identifiers-dids/create-a-did.md)
+    * [Update a DID](sdk/credo/decentralized-identifiers-dids/update-a-did.md)
+    * [Deactivate a DID](sdk/credo/decentralized-identifiers-dids/deactivate-a-did.md)
+  * [DID-Linked Resources](sdk/credo/did-linked-resources/README.md)
+    * [Create AnonCreds Schema](sdk/credo/did-linked-resources/create-anoncreds-schema.md)
+    * [Create AnonCreds Credential Definition](sdk/credo/did-linked-resources/create-anoncreds-credential-definition.md)
+  * [Verifiable Credentials and Presentations](sdk/credo/verifiable-credentials-and-presentations/README.md)
+    * [Issue a Verifiable Credential](sdk/credo/verifiable-credentials-and-presentations/issue-a-verifiable-credential.md)
+    * [Present a Verifiable Credential](sdk/credo/verifiable-credentials-and-presentations/present-a-verifiable-credential.md)
+* [🍊 ACA-Py](sdk/aca-py/README.md)
+  * [Setup ACA-Py Agent](sdk/aca-py/setup-aca-py-agent.md)
+  * [Decentralized Identifiers (DIDs)](sdk/aca-py/decentralized-identifiers-dids/README.md)
+    * [Create a DID](sdk/aca-py/decentralized-identifiers-dids/create-a-did.md)
+    * [Update a DID](sdk/aca-py/decentralized-identifiers-dids/update-a-did.md)
+    * [Deactivate a DID](sdk/aca-py/decentralized-identifiers-dids/deactivate-a-did.md)
+  * [DID-Linked Resources](sdk/aca-py/did-linked-resources/README.md)
+    * [Create AnonCreds Schema](sdk/aca-py/did-linked-resources/create-anoncreds-schema.md)
+    * [Create AnonCreds Credential Definition](sdk/aca-py/did-linked-resources/create-anoncreds-credential-definition.md)
+  * [Verifiable Credentials and Presentations](sdk/aca-py/verifiable-credentials-and-presentations/README.md)
+    * [Issue a Verifiable Credential](sdk/aca-py/verifiable-credentials-and-presentations/issue-a-verifiable-credential.md)
+    * [Present a Verifiable Credential](sdk/aca-py/verifiable-credentials-and-presentations/present-a-verifiable-credential.md)
+    * [Revoke a Verifiable Credential](sdk/aca-py/verifiable-credentials-and-presentations/revoke-a-verifiable-credential.md)
 * [🍈 Veramo](sdk/veramo-plugin/README.md)
   * [Set up Veramo CLI for cheqd](sdk/veramo-plugin/setup/README.md)
     * [Troubleshooting Veramo CLI setup](sdk/veramo-plugin/setup/troubleshooting.md)
@@ -96,32 +121,7 @@
   * [DID-Linked Resources](sdk/veramo-plugin/did-linked-resources/README.md)
     * [Create a DID-Linked Resource](sdk/veramo-plugin/did-linked-resources/create-resource.md)
     * [Create a new Resource version within existing Collection](sdk/veramo-plugin/did-linked-resources/create-new-version.md)
-* [🍏 Credo](sdk/credo/README.md)
-  * [Setup Credo Agent](sdk/credo/setup-credo-agent.md)
-  * [Decentralized Identifiers (DIDs)](sdk/credo/decentralized-identifiers-dids/README.md)
-    * [Create a DID](sdk/credo/decentralized-identifiers-dids/create-a-did.md)
-    * [Update a DID](sdk/credo/decentralized-identifiers-dids/update-a-did.md)
-    * [Deactivate a DID](sdk/credo/decentralized-identifiers-dids/deactivate-a-did.md)
-  * [DID-Linked Resources](sdk/credo/did-linked-resources/README.md)
-    * [Create AnonCreds Schema](sdk/credo/did-linked-resources/create-anoncreds-schema.md)
-    * [Create AnonCreds Credential Definition](sdk/credo/did-linked-resources/create-anoncreds-credential-definition.md)
-  * [Verifiable Credentials and Presentations](sdk/credo/verifiable-credentials-and-presentations/README.md)
-    * [Issue a Verifiable Credential](sdk/credo/verifiable-credentials-and-presentations/issue-a-verifiable-credential.md)
-    * [Present a Verifiable Credential](sdk/credo/verifiable-credentials-and-presentations/present-a-verifiable-credential.md)
 * [🫐 Walt.id Community Stack](sdk/walt-id.md)
-* [🍊 ACA-Py](sdk/aca-py/README.md)
-  * [Setup ACA-Py Agent](sdk/aca-py/setup-aca-py-agent.md)
-  * [Decentralized Identifiers (DIDs)](sdk/aca-py/decentralized-identifiers-dids/README.md)
-    * [Create a DID](sdk/aca-py/decentralized-identifiers-dids/create-a-did.md)
-    * [Update a DID](sdk/aca-py/decentralized-identifiers-dids/update-a-did.md)
-    * [Deactivate a DID](sdk/aca-py/decentralized-identifiers-dids/deactivate-a-did.md)
-  * [DID-Linked Resources](sdk/aca-py/did-linked-resources/README.md)
-    * [Create AnonCreds Schema](sdk/aca-py/did-linked-resources/create-anoncreds-schema.md)
-    * [Create AnonCreds Credential Definition](sdk/aca-py/did-linked-resources/create-anoncreds-credential-definition.md)
-  * [Verifiable Credentials and Presentations](sdk/aca-py/verifiable-credentials-and-presentations/README.md)
-    * [Issue a Verifiable Credential](sdk/aca-py/verifiable-credentials-and-presentations/issue-a-verifiable-credential.md)
-    * [Present a Verifiable Credential](sdk/aca-py/verifiable-credentials-and-presentations/present-a-verifiable-credential.md)
-    * [Revoke a Verifiable Credential](sdk/aca-py/verifiable-credentials-and-presentations/revoke-a-verifiable-credential.md)
 
 ## 🏗️ Architecture
 
@@ -135,6 +135,13 @@
 
 ## 💫 Advanced features and alternatives <a href="#advanced" id="advanced"></a>
 
+* [💡 Build Trust for AI Agents](advanced/ai-agents/README.md)
+  * [Build an AI Agent Trust Registry](advanced/ai-agents/build-trust-registry.md)
+  * [Issue Verifiable Credentials to AI Agent](advanced/ai-agents/issue.md)
+  * [Validate AI Agent Trust Chain](advanced/ai-agents/validate.md)
+  * [MCP Server Setup](advanced/ai-agents/mcp/README.md)
+    * [Issue a Verifiable Credential](advanced/ai-agents/mcp/issue-a-verifiable-credential.md)
+    * [Verify a Credential](advanced/ai-agents/mcp/verify-a-credential.md)
 * [➡️ DID Registrar](advanced/did-registrar/README.md)
   * [Setup DID Registrar](advanced/did-registrar/did-registrar-setup.md)
   * [Create a DID](advanced/did-registrar/create-did.md)
@@ -158,16 +165,6 @@
   * [VDR Tools CLI with cheqd (deprecated)](advanced/tooling/vdr-tools.md)
   * [Demo Wallet for identity setup](advanced/tooling/demo-wallet.md)
 
-***
-
-* [💡 Build Trust for AI Agents](ai-agents/README.md)
-  * [Build an AI Agent Trust Registry](ai-agents/build-trust-registry.md)
-  * [Issue Verifiable Credentials to AI Agent](ai-agents/issue.md)
-  * [Validate AI Agent Trust Chain](ai-agents/validate.md)
-  * [MCP Server Setup](ai-agents/mcp/README.md)
-    * [Issue a Verifiable Credential](ai-agents/mcp/issue-a-verifiable-credential.md)
-    * [Verify a Credential](ai-agents/mcp/verify-a-credential.md)
-
 ## ⚛️ Network
 
 * [Get started with cheqd Network](network/cheqd/README.md)

ai-agents/README.md renamed to advanced/ai-agents/README.md

@@ -1,5 +1,5 @@
 ---
-description: Design and Build Trust Registries for AI Agents
+description: Design and Build Trust Registries for AI Agents on cheqd.
 ---
 
 # 💡 Build Trust for AI Agents
@@ -22,10 +22,6 @@ If you are already aware of how cheqd's Decentralized Trust Chains (DTCs) are st
 
 <table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Build an AI Agent Trust Registry</strong></mark></td><td>Establish a comprehensive ecosystem for trusted AI Agents, organisations and governance authorities.</td><td><a href="build-trust-registry.md">build-trust-registry.md</a></td></tr><tr><td><mark style="color:blue;"><strong>Issue Verifiable Credentials to AI Agent</strong></mark></td><td>Using your Trust Registry, issue your AI Agent a credential fully referencing the Trust Chain back to a Root DID.</td><td><a href="issue.md">issue.md</a></td></tr><tr><td><mark style="color:blue;"><strong>Validate AI Agent Trust Chain</strong></mark></td><td>Use our Validation APIs to enable your AI Agent to autonomously prove that it is trusted and accredited.</td><td><a href="validate.md">validate.md</a></td></tr></tbody></table>
 
-
-
-
-
 ## Establishing a Trust Hierarchy <a href="#hierarchy-examples" id="hierarchy-examples"></a>
 
 cheqd's Trust Registry model is predicated on the notion of a trust hierarchy, which is conceptually very similar to traditional Public Key Infrastructure (PKI). Specifically, the model relies on a **Root of Trust** from which trusted relationships can be established.
@@ -34,13 +30,13 @@ In our model for AI Agents, each organisation in the trust hierarchy is able to
 
 The following diagram shows an example of how an AI Agent Creator can accredit two AI Agents lower in the hierarchy:
 
-<figure><img src="../.gitbook/assets/AI Agent Trust Registries.jpg" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/AI Agent Trust Registries.jpg" alt=""><figcaption><p>Root DID (rTAO) accrediting or authorising sub-DIDs (TAOs)</p></figcaption></figure>
 
 Through this type of relationship, an AI Agent can prove that it is accredited by an AI Agent Creator through presenting the Verifiable Accreditation, which is stored on the cheqd blockchain.
 
 Similarly, an AI Agent creator can prove that it is also trustworthy, demonstrating that it is a real actor rather than a fraudulent actor. In the diagram below, a Governance Authority (such as an accreditation body for AI Agent Creators) can accredit AI Agent Creators directly.
 
-<figure><img src="../.gitbook/assets/AI Agent Trust Registries (Governance Authority).jpg" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/AI Agent Trust Registries (Governance Authority).jpg" alt=""><figcaption><p>Full tree diagram of root DID accrediting DIDs, that accredit AI Agents.</p></figcaption></figure>
 
 Therefore, relying parties can query the accreditations of AI Agents all the way back to a Root of Trust.
 

ai-agents/build-trust-registry.md renamed to advanced/ai-agents/build-trust-registry.md

@@ -10,13 +10,13 @@ Users are able to build AI Agent Trust Registries using our cheqd Studio APIs. T
 
 Make sure you have set up your account with **cheqd Studio** and are logged in, using our guide below:
 
-<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Set up your account</strong></mark></td><td>Set up your account with <strong>cheqd Studio</strong> and log in to start using the APIs.</td><td><a href="../getting-started/studio/set-up-account.md">set-up-account.md</a></td></tr></tbody></table>
+<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Set up your account</strong></mark></td><td>Set up your account with <strong>cheqd Studio</strong> and log in to start using the APIs.</td><td><a href="../../getting-started/studio/set-up-account.md">set-up-account.md</a></td></tr></tbody></table>
 
 ## Step 2: Create a Root DID
 
 The first step for any trust registry is a Root DID, which acts as a trust anchor for the chain of trust below. This DID should be for the highest level of trust in your ecosystem, such as a governance authority, or a managing company.
 
-<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Create an Issuer DID</strong></mark></td><td>Create a W3C conformant DID on cheqd using the <code>did:cheqd</code> DID Method.</td><td><a href="../studio/dids/create-did.md">create-did.md</a></td></tr></tbody></table>
+<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Create an Issuer DID</strong></mark></td><td>Create a W3C conformant DID on cheqd using the <code>did:cheqd</code> DID Method.</td><td><a href="../../studio/dids/create-did.md">create-did.md</a></td></tr></tbody></table>
 
 ## Step 3: Design Schemas for your Ecosystem
 
@@ -541,7 +541,7 @@ With the Root DID you created in Step 2, you can create links to your schemas, s
 
 You can follow the tutorial here to publish your schemas as DID-Linked Resources. Generally we use the `resourceType` of `JSONSchemaValidator2020` for JSON schemas written.
 
-<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Create DID-Linked Resource</td><td>Link resources such as schemas to your DID, publishing as a DID-Linked Resource.</td><td><a href="../studio/did-linked-resources/">did-linked-resources</a></td></tr></tbody></table>
+<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Create DID-Linked Resource</td><td>Link resources such as schemas to your DID, publishing as a DID-Linked Resource.</td><td><a href="../../studio/did-linked-resources/">did-linked-resources</a></td></tr></tbody></table>
 
 This will store the schemas securely on the cheqd Network, where they can be fetched using DID URLs.
 

ai-agents/issue.md renamed to advanced/ai-agents/issue.md

@@ -10,7 +10,7 @@ Once you have created your Trust Registry for the accreditation and authorisatio
 
 Each AI Agent will need to be identified by its own DID, to which it will receive credentials and/or accreditations. This enables the AI Agent to be cryptographically able to assert control over these credentials and/or accreditations.
 
-<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Create an Issuer DID</strong></mark></td><td>Create a W3C conformant DID on cheqd using the <code>did:cheqd</code> DID Method.</td><td><a href="../studio/dids/create-did.md">create-did.md</a></td></tr></tbody></table>
+<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Create an Issuer DID</strong></mark></td><td>Create a W3C conformant DID on cheqd using the <code>did:cheqd</code> DID Method.</td><td><a href="../../studio/dids/create-did.md">create-did.md</a></td></tr></tbody></table>
 
 ## Step 2: Choose Schema for Credential
 
@@ -146,7 +146,7 @@ The Issuer should use this tutorial to publish the credential as a DID-Linked Re
 
 You can follow the tutorial here to publish your issued credential as a DID-Linked Resource. Generally we suggest the `resourceType` of `VerifiableAttestation` for credentials issued to AI Agents.
 
-<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Create DID-Linked Resource</td><td>Link resources such as schemas to your DID, publishing as a DID-Linked Resource.</td><td><a href="../studio/did-linked-resources/">did-linked-resources</a></td></tr></tbody></table>
+<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Create DID-Linked Resource</td><td>Link resources such as schemas to your DID, publishing as a DID-Linked Resource.</td><td><a href="../../studio/did-linked-resources/">did-linked-resources</a></td></tr></tbody></table>
 
 This will store the schemas securely on the cheqd Network, where they can be fetched using DID URLs.
 

ai-agents/mcp/README.md renamed to advanced/ai-agents/mcp/README.md

@@ -123,7 +123,7 @@ Add the following configuration to your claude\_desktop\_config.json or .cursor/
 
 When successfully started, the number of tools available to Claude Desktop will increase.
 
-<figure><img src="../../.gitbook/assets/Screenshot 2025-03-28 at 16.46.59.png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/Screenshot 2025-03-28 at 16.46.59.png" alt=""><figcaption></figcaption></figure>
 
 {% hint style="warning" %}
 There may be a error on top right corner, but it can be safely ignored. It is because of port binding, as Claude creates two processes for each MCP Server.